What the journal records
- Inputs and their sources: what materials arrived at the stage.
- Stages and states: what is done, what is stopped, what is waiting for a human.
- Basis for conclusions: every key conclusion references an observation, a source, or an explicitly stated assumption.
- Fragments recognized without confidence are marked for human verification.
Traceability in the products
- Local meeting scribe: an event journal — what data came in, what stages were completed, on which content each document was formed; the reports are cross-checked against the original recording.
- Business Requirements Analyst: an audit ledger with full replay of changes — every requirement is tied to a fragment of the source.
- CustDev agent: an opportunity map with links to the primary fragments of the interviews.
- Super Oracle: assumptions and risks are named separately from the solution directions.
Why the business needs it
The journal turns the result from the "opinion of the system" into material with an evidence base: checking a conclusion takes minutes, responsibility for the decision is clear, a new employee sees how the artifact was obtained, and an audit gets a reproducible history of the launch.
The journal does not replace verification
The journal shows the path of the result but does not make it true: critical conclusions are confirmed by a human with the right competence. That is why in the agent passport the journal and verification go together.
Questions and answers
Can the journal be exported?
The format depends on the agent: the meeting scribe keeps an event journal, while the requirements analyst keeps a replayable audit log. The details are defined during the assessment.
How is the journal different from chat history?
Chat history records the conversation. The journal records inputs, stages, decisions, and the basis for each conclusion, so the result can be reproduced and reviewed.
Who reads the journal?
The person responsible for the process: they check disputed conclusions and confirm decisions. In a team environment, access to the decision journal is assigned by role.
What does the journal record?
Inputs, stages, decisions and sources: the result is traceable back to the source data.
Is the journal created automatically?
Yes. Each stage is recorded as the work progresses, and the journal is included in every deployment regardless of the engagement model.
Can a journal entry be changed?
The journal describes the actual course of work; changes to permissions and decisions are recorded as new events.
Does the journal help when there is an error?
Yes. The trace shows which stage and source data produced the problematic conclusion.
Who has access to the journal?
The person responsible for the process; in a team environment, access is assigned by role.
How is the journal different from model logs?
The journal describes the process stages, inputs and decisions, not the internal workings of the model.
Is the journal mandatory for a subagent?
Yes. The passport, work journal, and traceability are included in every deployment, including subagent deployments.