Source-linked records
Claims retain their source, attribution and qualifications. Review helps inspect the record; it does not establish truth.
Section pages
Context Capsules / The knowledge format
Portable context.
The graph comes with it.
A Context Capsule is designed to package sources, claims, relationships, time and analytical methods. The aim is to carry a usable record into the next question, workspace or AI tool.
PRAXIS supports document-to-capsule review and reuse in chat. Reference bundles include additional graph structures. Full lossless interchange remains in development.
What travels together
Meaning, connections
and the evidence behind them.
The ontology defines a proposal, a condition or a decision. The graph connects them. The capsule is designed to preserve those connections alongside source references and review state.
Context, connectedFictional policy case
An ontology gives each record a meaning. The graph connects the proposal to its source, author, conditions and review.
Select a record to follow its connections. Small screen? Scroll the graph.
ClaimProposed pilotProposal · not approved
A proposal is distinct from an adopted policy. Funding and approval remain unresolved in this example.
Policy memo records Proposed pilotMinistry proposes Proposed pilotProposed pilot depends on Funding conditionProposed pilot response by 30 June responseProposed pilot requires Committee approvalCheck conditions checks Proposed pilot
One structure · four types
Who you are. What’s happening. How experts think. What good looks like.
Four ways to organize the context a task needs. Download the illustrative JSON files to inspect the proposed format. Support for the full design is still in development.
User capsule
Who you work as: role, mandate, audience, voice, standing positions.
Built from: A conversation plus your past documents.
example .jsonSituation capsule
What is going on: actors, claims, events, contradictions, episodes.
Built from: Your documents, feeds, and a guided interview.
example .jsonTool capsule
How an expert thinks: methods, heuristics, traps, checklists, devices.
Built from: An expert-elicitation interview.
example .jsonOutput capsule
A reviewed work product: audience, sources, provenance, version and caveats.
Built from: A reviewed deliverable and its source and review record.
example .jsonThe proposed anatomy · nine layers
01Evidence
02Claims
03Graph
04Temporal
05Ontology
06Reasoning
07Memory
08Governance
09Runtime
Authored context landscape
From individual records
to a connected graph.
A fictional reporting-rule assignment within 640 authored synthetic records and eight dossiers. The fixture download preserves the same passages, relationships, snapshots and capsule membership. Illustration size is not product scale.
Authored context landscape / fictional
One assignment. A connected record.
640synthetic records8dossiers
Example Advisory is following a reporting-rule consultation. Inspect a proposal, the passage behind it and what changes on Day 15. The other dossiers illustrate the same structure. Illustration size is not product scale.
View communication layers
Teaching lenses over these same records. They are distinct from four capsule roles and nine architecture responsibilities.
Choose a layer to see its records. Selection is preserved; Reset filters returns the full landscape.
100%
◇ Claim · ▭ Source · △ Evidence · ○ Actor · □ Organization · + Event · ▽ Constraint · ⬡ Method · × Review · ▣ Output
Overview uses selective labels; relevant paths appear on selection.
Search and inspect records
Explore the authored records as the landscape prepares.
Record list
Preparing record controls. Read the complete authored fixture.
Record unavailable
The requested record is missing. Choose a result in the list.
Inside the idea · interactive architecture explainer
A shareable graph of context. More than a document bundle.
Think of a Context Capsule as a small, versioned knowledge database: several connected layers that a person can inspect and a compatible agent can query. These six views explain the design; they are not a claim that every layer is fully implemented in PRAXIS.
Evidence layer
Where did this come from?
Documents, excerpts, source dates, permissions, and provenance. A claim should lead back to the material that supports it. A citation is inspectable evidence, not a guarantee that the claim is true.
Document → paragraph → claim · source access stays explicit
Portability is a development target. PRAXIS export/import currently needs work to preserve document and workspace references. A reference capsule demonstrates a format; it does not establish cross-tool compatibility or source-sharing permission.
Reference artifacts
Inspect the actual files.
Four engine-compiled examples. Open their JSON, manifests and sections, or download a bundle.
loading example…
Reference formats do not establish four complete PRAXIS authoring paths. Historical asset redistribution terms are unconfirmed; ask before redistribution. Scenario rights fields do not license the downloaded file. Use and licensing.
Under the hood
Open structure. Explicit boundaries.
A queryable graph
Reference artifacts explore JSON-LD and an embedded read-only graph projection. PRAXIS exports have different capabilities.
Methods and review
Keep the questions an analyst asks, the evidence still needed and the decisions a reviewer made.
DIALECTICA is the Rust knowledge-engine development behind the format. Signing and full revision/diff workflows remain roadmap items.
Use the context
Put a capsule to work in PRAXIS.
Upload documents, review proposed context and attach a saved capsule to your question. Shared discovery through a Capsule Registry remains a proposal.