Evidence and provenance
Research, documents, observations and source history remain attached to the claim they support.
Trusted memory architecture
Carry the mission forward without losing the why.
Vault is the memory role inside GhostGrid: preserve evidence, decisions, ownership, confidence and outcomes so the next run begins with context instead of restarting from scratch.
What belongs in memory
Not just files. The chain of reasoning.
A useful operational memory connects the artifact to its source, confidence, decision, owner, next action and result. That is what makes earlier work reusable.
Decisions and commitments
What was decided, by whom, under which assumptions and what must happen next.
Outcomes and learning
Results feed the next loop so the system can improve from what actually happened, not what was expected.
Control model
Memory must respect authority.
Vault is designed around scoped access, explicit write paths and reviewable provenance. The public website does not provide a storage interface or expose any private Vault content.
Design principle
Need-to-know context
Mission roles should receive the minimum context required to do their work—not unrestricted access to everything.
Design principle
Explicit writes
New facts, changes and external actions should move through named contracts and preserve their source.
Design principle
Conflicts stay visible
Contradictory evidence should be surfaced for review instead of silently collapsed into false certainty.
Public boundary
No operational memory is served here.
This Hostinger page explains Vault’s role. It does not connect to the separate VPS, retrieve customer records or provide a path into production storage.