Identity
ID, title, owner, date, scope, status and reversibility.
KhaiTriOS · Decision Graph & Memory
Decisions deserve more than memory.
The decision library preserves what was known, which alternatives were considered, why one path was chosen, what it cost and what later evidence says about it.
Why decision records
A final choice is less useful when its original context disappears.
Projects remember outputs more easily than reasoning. Without context, future work either repeats the same debate or copies an old decision into a new situation where it no longer fits.
A decision record keeps the problem, constraints, alternatives, criteria and consequences together. Later evidence can confirm, refine, reverse or supersede the choice without rewriting history.
The public library only contains decisions that can be explained safely. Personal memory, credentials, private strategy and client-sensitive reasoning remain outside the website.
Decision record schema
Every record uses the same eight-part operating contract.
Consistency makes decisions comparable across projects without forcing every decision to have the same outcome.
Context
The trigger, problem, constraints and facts known at decision time.
Options
Real alternatives considered, including the cost of doing nothing.
Criteria
Impact, evidence, reversibility, operating cost and decision-specific standards.
Decision
The chosen path and concise rationale connecting it to the criteria.
Consequences
Benefits, trade-offs, risks, new obligations and rejected benefits.
Evidence
Outcomes, measurements, related projects and signals collected later.
Review
Triggers, review date or phase, status changes and superseding records.
Published records
Accepted decisions with public-safe reasoning.
The first record establishes the architectural boundary that makes the rest of KhaiTriOS publishable.
System architecture · Privacy
Separate public knowledge from private memory
Publish reusable proof, principles and decisions while keeping credentials, personal memory, client data and sensitive AI context in a protected layer.
Open decision record Read linked lessonStatus model
Decision history changes status, not the original record.
Under consideration
Context and alternatives are documented, but the choice is not yet active.
Current operating choice
The decision is active and should guide related work.
Intentionally undone
Later evidence caused the system to return to a previous or alternative path.
Replaced by a newer record
The original reasoning remains visible and links to the decision that replaced it.
No longer operational
The decision belonged to a system or context that no longer exists.
Candidate records
The next decisions will connect project choices to reusable evidence.
Use static-first architecture for public websites
Capture when static delivery is preferred and which signals justify adding backend complexity.
Separate editable sources from generated outputs
Preserve the source-of-truth rule across spreadsheet-powered and template-generated sites.
Require human approval for consequential automation
Define where automated preparation ends and accountable approval begins.
Foundation status
The public decision layer is operational.
The schema, status model and first accepted record now provide a foundation for connecting future choices to evidence and lessons.