Context LogicChief of Staff Context Logic
Study the active CoS context-ledger model. The Chief of Staff keeps source truth in context/, routes scoped packets to specialists, and treats Hub/manifests as retired unless explicitly reactivated.
The Context Pipeline Flow
1. Source Registry
CoS declares what may be checked.
The active source registry lives in the CoS workspace under context/sources.json and companion inventory files. It replaces older Hub/context-map assumptions and keeps source scope explicit before any refresh or route.
File-Based Ledger Registry
The context tracking system is lightweight and file-driven, located inside the Chief of Staff workspace directory. It uses a small ledger set to organize context state:
Machine-readable config defining the proactive channels, types, and read budgets.
Stores cursor metrics (latest Slack timestamp checked, watched Git commit SHAs).
Human-readable summary of operational facts, active pilots, and open questions.
Reviewable evidence and scoped handoff material used before specialist work.
Context Refresh Cadences
To optimize token bandwidth while keeping agents informed, the context keeper uses distinct, automated task sweeps scheduled via Kwanda Ops:
CoS Kwanda Ops tasks run heavy context refreshes at 07:15 and 15:15 SAST.
CoS light refresh runs hourly at minute 5 to keep high-signal deltas warm.
Research and Work also have AM/PM context refresh tasks and must run preflight before source-dependent work.
V1 Implementation Scope Warning
Important: V1 of the Company Agents website acts as a static documentation guide. Runtime facts were inspected read-only, curated into content files, and documented in the audit note. No Slack queries, Kwanda writes, Git writes, or runtime refreshes are initiated by this website.