01
Collect evidence locally
The system ingests permitted local history from version control, work sessions, memory and exported or read-only work tools. Every item retains its source, time and identity instead of becoming an unattributed summary.
Normal reads do not contact external providers. Refresh is a separate operation with an explicit scope.
02
Separate reconstruction from interpretation
Deterministic code normalizes timestamps, identities and relationships. A model can then classify or summarize a bounded evidence packet without inventing the underlying activity graph.
This makes it possible to correct a model conclusion without losing the evidence that produced it.
03
Preserve provenance and confidence
Every suggestion links back to the evidence used and records what could not be confirmed. Sensitive or ambiguous material stays private and reviewable.
Confidence is not a permission level. A high-confidence suggestion still needs the authority required by the destination system.
04
Keep external writes explicit
Drafting and posting are separate states. The exact message, comment or change is shown before the user approves the external action.
That boundary turns AI into an analysis and preparation layer while the human remains the accountable operator.