Atlas project production

Lifecycle Decision Queue

Compact decision queue for unresolved active vs fallback-only vs dormant/deprecated classifications.

Internal-only entry. Do not publish externally without review.
Type
System
Lifecycle
Active
Last touched
2026-03-26
Visibility
Internal

Purpose

Make remaining lifecycle decisions precise by documenting current evidence and exact proof needed for final status assignment.

Current state

Implementation remains present across all listed components, but scheduler/runtime evidence differs and final lifecycle outcomes are not fully closed.

Next step

Use this queue during ownership/review sessions to classify each item as active, fallback-only, dormant, or deprecated with explicit evidence.

Interfaces

Inputs
  • workflow implementation pages
  • scheduler evidence artifacts
Outputs
  • lifecycle-decision checklist

Reality to Action trace

Reality Ingestion

Not in scope.

Canonical Storage

Not in scope.

Automation Engines

Not in scope.

Human Interfaces

Not in scope.

Operational Adoption

Contributes in this stage.

Core workflow

TBD. Document the 5-10 steps that define the core workflow.

Data integrity and contracts

Source of truth rules

  • Implementation presence is not enough to classify as active.
  • Scheduler evidence and operator ownership must be explicit before active classification.

Safe handling

  • Keep internal host/path details within approved documentation boundaries.

Operational notes

Reliability posture

This queue is intentionally evidence-driven. It does not classify by assumption and keeps required proof explicit.

Observability

  • Atlas lifecycle updates on target pages

Security and privacy

Internal operational classification notes; keep internal.

Dependencies

Upstream
  • runtime-host-and-scheduler-reference
  • owner-escalation-and-fallback-matrix
Downstream
  • final workflow lifecycle classifications

Ownership

Owners

Technology Services, Josh Barton

Users

Technology Services, integration maintainers

Lifecycle Decision Queue

Decision Grid

ProjectImplementation still presentCurrent scheduler evidence statusLikely current roleEvidence needed for activeEvidence needed for fallback-onlyEvidence needed for dormant / deprecated
APEXLearningAPIYes (confirmed)No task evidence in saw-01 scheduler artifact; no reference in aether/docs/cron-example.txt (confirmed)Manual/legacy helper (likely)Current host/scheduler or documented manual production trigger + named technical operator + recent run evidenceNamed contingency workflow that still invokes helper, plus fallback owner/approval boundaryOwner confirmation that no active consumers remain and successor path is authoritative
GSuiteAPIYes (confirmed)No GSuiteAPI task paths in current saw-01 artifact; successor-like script names shown in aether cron docs (confirmed)Legacy overlap/reference repo (likely)Direct production invocation evidence from this repo paths + operator ownership + schedule/trigger evidenceScript-level list of retained fallback scripts with owners and trigger conditionsFinal migration map showing scripts superseded/retired with owner sign-off
mssql_query_to_google_sheetYes (confirmed)No direct saw-01 task entries; no direct aether cron reference (confirmed)Helper-only or dormant utility (likely)At least one current production workflow proving invocation path, host, cadence, and operator ownershipExplicit list of workflows where tool is retained only for exception/manual fallbackConfirmation that successor tools cover all use cases and no production invocations remain
Integr8r-rebaseYes (confirmed)Current saw-01 tasks invoke C:\Integr8r\Integr8r.ps1, not rebase path (confirmed)Runtime-adjacent variant/mirror (likely)Host task evidence invoking rebase path or explicit production runbook assigning active runtime roleExplicit standby/fallback designation with activation trigger and operator/escalation ownersGovernance decision that legacy Integr8r path is authoritative and rebase is non-runtime