command hub · the plan is the interface

Atlas importer rewrite

Get the new importer through one shadow week with no unexplained variance. The tree below is the work. Agent placement is remit: the lead sits at the root, an area owner sits on its branch, and specialists can sit directly on leaves. Open a goal to inspect its disposable workers and their worktrees, answer beside the goal that stopped, and use Send & pause when the conversation itself should keep new workers away until you resolve it.

atlas-lead Coordinates the whole rewrite: routes decisions, watches progress, and changes focus wherever the tree needs it. Its placement is the project-wide remit; it does not pretend to have one leaf assignment. Groundwork Snapshot the import corpus Nine months pinned by content hash. Build the replay harness Old and new importer over the same corpus. Map the legacy schema Every downstream field has an owner. Replace the XML parser Two workers own separate worktrees; the whole row opens both. The stalled dedupe leaf filed itself around this goal rather than turning a worker into a pet. w-1 Parser area owner; focused now on declarations and entity boundaries, but responsible for this whole branch of the plan. Declarations and entities Three new corpus cases remain. Streaming core Constant memory over the full corpus. CDATA edge cases Eleven legacy exports replay cleanly. w-2 CDATA specialist: escaped-markup corpus cases. Deduplicate the corpus snapshot Three hours of worker activity produced no commit. Last worktree: atlas/dedupe-attempt. w-5 Dedupe specialist, reaped after three hours without a commit; its branch and evidence remain inspectable.

What should the host do with the stalled work?

Restart with a fresh worker Preserve the branch, commits, and comments; reap the old worker. My take: keep the durable work and replace the stalled process. Park it for tomorrow Keep the branch and take it out of today's plan. Drop it Archive the branch; corpus storage stays at 40 GB for this rewrite. Choose the zero-row behavior This policy is consequential enough to wait for an explicit choice.

What should happen when a nightly imports zero rows?

Fail and page Preserve the export and stop the downstream publish. My take: zero rows is a failure until proved otherwise. Warn and continue Record the empty import but publish no data. Reconcile schema and ledger Two goals and the nightly wait behind the schema choice. Choose the additive schema Both columns are nullable; the migration and reverse path are green. w-8 Schema-choice specialist: migration and reconciliation evidence.

What should the host do with the schema branch?

Land it now Tests are green, it unblocks the dependent work, and shadow reads begin before anything depends on it. My take: land while the evidence is current. Hold for the backfill Keep the dependent work idle and take one larger review tomorrow. Backfill reconciliation fields Bring one replica-only ledger fixture Run the exact credentialed command, inspect the full cargo below, trim it, then save the draft. The edit receipt tells the orchestrator that w-8 can resume.

Which replica-only ledger fixture should the worker use?

psql "$ATLAS_REPLICA" -c "\copy (select * from ledger_entry
  where refunded_minor is not null limit 1) to stdout with csv header"
Paste the complete CSV row here. Remove customer_name and billing_email before saving.
Nightly variance report Unreachable until both inputs stand. Publish the parser contract Review the branch, not its author. A line comment routes to a fresh evidence worker and stays anchored here. Review the public result type w-3 Public-contract specialist: result types and compatibility tests.

What should the host do with atlas/public-api?

Land The compatibility suite is green. My take: the public contract is ready. Request changes Restate this card and dispatch a fresh revision worker; the request remains in the record. Land as-is — discard revision Explicitly overtake a standing change request and reap its reviser. Map structured failures Regenerate the SDK fixture Document the operator path Write the replica runbook Write rollback and evidence capture Cut over the nightly This goal is visibly downstream of both schema and ledger evidence. Shadow both importers for one week Swap with the old path behind a flag

The record

Every consequential gesture lands here in order. Folds are read-only and stay out; comments, pauses, decisions, reports, and releases remain as receipts even after the work around them changes.