Observations
Raw source objects, records, sensor events, messages and documents.
PUBLIC FRAMEWORK
The ContextWeaver context model.
A public-safe reference model for converting fragmented information into an authority-aware, evidence-governed operational context.
FOUNDATIONAL DISTINCTION
A model can receive relevant information and still lack valid operational context.
Relevance is not authority.
Information can be relevant but stale, unauthorised, contradicted, privileged, geographically restricted or unsuitable for the requested action. ContextWeaver therefore represents context as a composite state rather than a text window.
The framework can sit around retrieval-augmented generation, knowledge graphs, workflow engines, agent runtimes, repositories, enterprise applications and human decision processes.
DEPTH MODEL
Context becomes operational through progressive control.
Each level adds information needed to determine whether an output or action may be relied upon or released.
Normalised records
Parsed content, identifiers, metadata, classifications and source references.
Linked context
Entities, relationships, dependencies, semantic links and graph position.
Temporal and causal state
Event sequence, freshness, expiry, supersession, causal claims and uncertainty.
Identity and authority
Person, organisation, model, agent, device, role and delegation status.
Policy and risk
Rules, jurisdiction, confidentiality, risk thresholds and prohibited operations.
Federated interpretation
Model and agent assessments, disagreement, confidence and evidence weighting.
Execution control
Allow, constrain, defer, deny, exception handling and human escalation.
Release and licence
Reliance, disclosure, audience, commercial entitlement, revocation and expiry.
Institutional memory
Version lineage, precedent, learning, policy evolution and recursive governance.
CONTEXT ENVELOPE
A portable decision boundary.
A context envelope accompanies a proposed operation across models, agents, tools and organisations.
| Field group | Representative content | Control purpose |
|---|---|---|
| Purpose | Requested objective, task class, intended audience and permitted use. | Prevents reuse outside the authorised purpose. |
| Sources | Identifiers, origin, custody, freshness, classifications and transformation history. | Establishes what the system is relying upon. |
| Authority | Identity, role, delegation, approval requirement and final accountable authority. | Separates assistance from accountable decision-making. |
| Policy | Jurisdiction, organisational rules, prohibited operations, exceptions and escalation. | Defines the executable boundary. |
| Evidence | Reliability class, conflicts, verification state, hashes, signatures and receipts. | Preserves reviewability and custody. |
| Release | Confidentiality, recipient class, licensing terms, expiry, revocation and reliance limits. | Controls what may leave the system and on what terms. |
Review the implementation architecture.
The framework is deliberately vendor-neutral and can be mapped to existing enterprise systems.