[ZASI v33 P6] Chief-of-Staff orchestration: Goals/Tasks/Runs, Memory Router, executive brief and productivity connectors #15

Objective

Evolve ZASI from a command cockpit into a governed Autonomous Chief-of-Staff runtime that plans durable work, retrieves scoped context, uses connectors, verifies outcomes and reports only source-backed facts.

Source-grounded findings

• ZASI already has MCTSPlanner, DynamicHypergraphMemory, PersistentHypergraphStorage, personas, MCP and an autonomous daemon, but they are not composed into a durable Goal→Task→Run application model.
• Hypergraph memory is an in-memory graph plus SQLite serialization; no project/tenant provenance router or retrieval budget is present.
• The latest APEX-inspired Morning Brief uses fixed values such as 176 subsystems, 178.2 GW and 3,500 ExaFLOPs.
• Current repo has no durable productivity connector layer for GitHub/email/calendar/files within a common policy/evidence boundary.

Scope

• Add persistent Goal, Task, Run, dependency, schedule, priority, outcome and artifact models.
• Build Goal→Plan→Task DAG→Run→Verify→Persist→Report lifecycle on top of the existing planner.
• Add durable scheduler: next-run time, lease, idempotency, missed-run policy, retry, dead-letter, cancellation and history.
• Introduce Memory Router with Core, Working, Episodic, Semantic and Project memory classes plus provenance, ACL and freshness invalidation.
• Build source-backed Executive/Morning Brief aggregator from actual telemetry, tasks, approvals, failures and connected sources.
• Add governed connector interfaces for GitHub, email, calendar, files and web through the action/egress broker.
• Track model/provider cost, latency, fallback and cache usage.

Acceptance criteria

• Restart does not lose queued/scheduled work.
• Duplicate scheduling cannot duplicate side effects.
• Task/run history reconstructs from durable events.
• Cross-project/tenant memory leakage tests pass.
• Stale memory is invalidated and provenance is visible.
• Missing connector data is shown unavailable/stale, never invented.
• Every executive brief claim links to evidence/source metadata.
• Pending approvals, failures and degraded connectors surface explicitly in the brief.

Depends on

#10 #11 #12 #13

Priority

P6 / core Chief-of-Staff capability.