Meaning
An allegation, a proposal and an approved commitment imply different things. An ontology makes those definitions explicit.
Explore the ontology →Section pages
Why context
The next question should inherit the context.
A policy brief depends on who said what, which commitments apply and what changed. That knowledge often stays scattered across documents, conversations and earlier drafts.
TACITUS is developing tools to make this record explicit. PRAXIS puts reviewed context to work today; portable graphs and cross-tool handover are the next engineering steps.
The practical value
Keep the distinctions an analyst needs.
Relationships
A graph connects claims to actors, source passages, conditions and time. Follow the connection when checking a conclusion.
Explore the graph →Continuity
A capsule is designed to carry that record, its analytical method and its caveats into the next task. Full interchange still needs validation.
Inspect a capsule →Seven communication layers / a reading aid
Read the assignment from different angles.
Assignment; people and organization; sources and provenance; documented actor positions; time and conditions; methods and assumptions; reviews and outputs. These overlapping lenses help a person navigate the same record. They are not product modules, capsule roles or architecture responsibilities.
A source folder does not carry the correction.
S01 preserves the January proposal. The useful addition is the scoped discipline: identify authority, separate requests from agreement and retain unresolved funding. In the local packet that method is pinned beside the passages, audience and cutoff. Saving the reviewed correction makes it available for the next assignment; the next analyst still rechecks applicability and missing evidence.
The technical idea
Give the next task a record
it can reason from.
Retrieval finds relevant material. Structure makes its meaning, relationships, and review state explicit. Explore how the parts are intended to work together.
Your evidence
Keep a claim close to its source.
Documents, passages, authors, and dates are the starting point. A statement should retain its origin and access boundary as it moves into structured knowledge.
- Receives
- Approved documents and a defined question
- Produces
- Source records with stable references
- Quality question
- Can a reviewer recover the passage and its context?
Illustrative record · Sources
- source id
- source-01
- passage
- The extension has been requested, not approved.
- record type
- statement
- access
- approved_for_this_task
Inspect the illustrative JSON
{
"source_id": "source-01",
"passage": "The extension has been requested, not approved.",
"record_type": "statement",
"access": "approved_for_this_task"
}Teaching example. This is not a production schema or an API response.
Architecture under development. Integration and portability require end-to-end validation.
Current capabilitiesThree organizing ideas / different jobs
Human context first.
Architecture beneath it.
In Example Advisory’s fictional assignment, the mandate, colleague’s correction, client audience, deadline, source accounts and approved method all matter. No rule has been adopted; optional pilot funding remains undecided.
Everyday context: what the team needs to remember
- Organization and mandate
- Geopolitical-risk advice; legal assurance is outside the assignment.
- Colleagues and review history
- Preserve the accepted correction: proposed timing is not adoption.
- Audience and situation
- A client steering group needs an explanation by Day 16.
- Evidence
- S01 proposes January, S02 requests transition, S03 considers July.
- Time
- Proposal, adoption, effective date and date known are different.
- Methods
- Compare documented positions and conditional scenarios.
Four capsule roles: what a reference package is for
- User
- Explicit professional preferences and perspective, including the role and mandate.
- Situation
- The dossier and its changing conditions, evidence, relationships and time.
- Tool
- Approved analytical methods and task configuration.
- Output
- A reviewed work product and its provenance, audience, version and qualifications.
Reference formats exist. Four roles do not establish four complete app editors.
Nine architecture responsibilities: how the design supports the record
- Evidence
- Preserve sources, passages, permissions and citations.
- Claims
- Separate statements, inferences, proposals and adopted commitments.
- Situation
- Bound the dossier, actors, conditions and assignment.
- Temporal
- Keep event, known, proposed effective and adoption dates distinct.
- Ontology
- Define record types and directional relationship meaning.
- Reasoning
- Expose analytical rationale, assumptions and alternatives; never a model’s private hidden reasoning.
- Memory
- Carry selected context and earlier review decisions forward.
- Governance
- Define human authority, versioned review and access boundaries.
- Runtime
- Execute bounded tasks, track proposed work and handle failures.
These are architecture responsibilities, not nine fully delivered modules. Their integrated operation requires implementation and evaluation.
AI workflows
Give the task a bounded record.
“Compare these positions” needs more than an instruction. Define the source set, preserve competing accounts, choose a method and specify what a human must check.
Context
The relevant evidence, relationships, time window and open questions.
Assignment
A defined output: a comparison, an options matrix or a challenge note.
Review
Check citations, assumptions and missing evidence before relying on the draft.
This is the agentic direction for PRAXIS. Structure helps review; improved analytical quality and reliable delegated work require evaluation.