Files
canina/specs/corporate-execution-observability/manual-plan-inventory-slice.md
2026-10-31 18:45:30 +00:00

4.4 KiB

Manual planned-action prerequisite (bounded slice)

Base develop 216e05ba. Existing dated plans contain BLOG_NEW and needs actions, whereas runtime only executes RESEARCH. Do not reinterpret inventory as article/enrichment completion.

Acceptance / plan

  • Explicit operator chooses persisted roadmap/month/task. Read exact PLANNED lineage, goal/date/action/source IDs and stored instruction. Validate lineage and due UTC day before any mutation.
  • Create a separately linked RESEARCH child with immutable structured planned_source_inventory_v1 instruction. Parent action remains pending (TODO normally; BLOCKED after child rejection), never published or auto-completed.
  • Targeted claim must not consume another queued task; preserve legacy claim idempotency. Execute exact stored source bytes selected by plan, store canonical snapshot/evidence, independently recompute during separate-identity QA.
  • PMO report after persisted child DONE must explicitly disclose original action pending; read report back. No models, synthesis, business adapter, external effect claim, cron, schema, approvals, production or publisher changes.
  • TDD: invalid/future/changed/missing lineage/source; exact snapshot; targeted claim; QA tamper; report readback. Focused and full backend/Python tests and backend build. Existing UI dossier is read-only inspection; no frontend change expected.

Review needs

This is genuine stored-source inventory, not new scientific research, clinical validation, publication or enterprise completion. Source bytes must already exist in the content-addressed operator store. Missing bytes fail closed; no network substitute. Stage engineering data is not an approved clinical roadmap. Parent owns review, commit, push and Stage acceptance.

Operation / recovery limits

Invoke python3 scripts/corporate_plan_inventory.py --store SECURED_STORE --key STABLE_KEY [--api API --allow-stage-https] prepare ROADMAP MONTH TASK, then execute CHILD, separate CORPORATE_QA_API_KEY identity qa CHILD EVIDENCE, then report CHILD. Each command is explicitly manual. Never pass credentials in CLI arguments. Require the original ingested source bytes in this store; no network fetch or provider output is substituted.

Stable prepare keys deduplicate exact requests only; different keys/actors can create additional children. Do not claim exactly-once prerequisites. Backend already allows only one report per UTC day; a pre-existing daily report is a conflict requiring operator reconciliation, not a reason to overwrite it. PMO summary records a status observation, not an atomic ongoing status guarantee.

Do not rerun execute to recover an ambiguous evidence POST: timestamps change. The digest printed to stderr before the POST points to the exact immutable path/body/key. Use the existing corporate_runtime.py replay-evidence DIGEST with the same secured store/identity for explicit exact-body replay after readback. Tests simulate an ambiguous transport response and prove this preserved request replays unchanged. QA/report reruns are not replay APIs; read persisted task/report and reconcile manually. No automatic retry or fabricated success. QA rejection recovery uses a new execution key; the original pending parent remains BLOCKED and is not unblocked by this adapter.

Verification receipt

Evidence /opt/data/content-maintenance/corporate-action-evidence-20261030/: initial missing-module RED, selector focused RED/GREEN copied from isolated claim evidence, happy-path HTTP focused GREEN, independent-review rejection RED/GREEN, final full backend and Python logs, backend/admin builds and full admin tests, source/log SHA256 manifest. Final backend: 105 suites/950 tests pass, existing 2 suites/3 tests skipped; Python: 27 pass. No commit/push/deploy. Initial admin commands failed because recovered clone lacked node_modules; reused existing dependencies only after byte-identical admin package-lock comparison, then full tests/build passed.

Graph SHA256 6a73473cee9e207543fdeeb668bea544f766200a1b16b8a3a9ce18d4e42e51af embeds older revision e7ded849f6b1e3bdab2a20d89b3ec7dd0df79cab, has no corporate/planner runtime nodes, and is navigation only; direct source/API/tests ground acceptance. No graph files were rewritten. Existing .specify/ preserved. No frontend source changed; existing execution dossier renders child description, evidence, QA and links, but monthly/report UX remains a dependency.