Record what is known, what is proposed and who decided
A source may support a statement without resolving the whole decision. Keep it and any contrary evidence alongside the proposal so a person can review it without confusing a suggestion with an agreement.
The destination is in Spanish. A waitlist does not guarantee immediate access or a free plan.
Situations to review
A budget labeled current and a draft contain different amounts.
Link each amount to the document, version, scope and excerpt. Distinguish the file’s label from verified applicability to this decision. If approval of the change is not established, leave it pending.
The newest file does not automatically win, and a draft is not presented as authorization.
Decision references are spread across conversations and documents.
Prepare an index by statement: relevant source, known date or version, supporting evidence, contradiction and unverified information. Restrict access and avoid unnecessary sensitive details.
Reviewers can follow available references and gaps. A link is not treated as a source already read or proof of the entire argument.
A collaborator proposes an action based on reviewed information.
Separate documented observations, the proposal and the human decision. Think² can organize context through groups, the option for each collaborator to have their own computer, compatible models and authorized tools. Record the decision owner and date only when established.
Preparing the record does not approve an action. External actions require approval; the record does not expose a model’s private reasoning.
How to evaluate the work
- Define one decision question and its scope. This record follows a specific decision and evidence rather than replacing a general project report or an access and retention policy.
- Link each statement to its source, location, known date or version and relevant excerpt. Record whether the source was read, its accessibility and limits. An uncorroborated statement stays unverified even if repeated in several summaries.
- Distinguish supported observations, interpretation, proposals and decisions. Preserve contradictions and limits without inventing an owner, date or consensus. Provenance helps review but does not certify compliance, truth or a correct decision. It does not reveal chain-of-thought or private reasoning.
- Template: question/scope; statement/type; source/version/excerpt; read status; support/contradiction; uncertainty; proposal; decision owner; decision/date/reference if known; action/approval. Fictional example: document A, labeled current budget, states 12,000 test-currency units; draft B states 15,000. The observed fact is that two differently labeled documents contain different figures. A’s applicability requires evidence, not just its title. Propose that the owner confirm the applicable amount, authorized source, validity and scope. Human decision: unknown. Do not choose B because it is newer or send an offer with an unresolved figure. This is not a real customer or verified integration.
Frequently asked questions
Does the record reveal how the AI thought internally?
No. It records sources, statements, proposals and observable decisions, not chain-of-thought or private reasoning.
Do sources prove a decision is correct?
No. A source can be incomplete, outdated or about another scope. Preserve contradictions and leave the decision to its owner with the limits visible.
Does a decision record certify compliance?
No. Provenance does not establish legal compliance, retention controls or an immutable audit trail. Those requirements need specific assessment and support.
Sources and scope
- W3C — PROV-O — Provenance concepts involving entities, activities and agents; not a prescribed template or decision certification.
- NIST — AI Risk Management Framework — A voluntary risk-management framework, not certification of a decision record or proof of a Think² integration.
Keep exploring
The destination is in Spanish. A waitlist does not guarantee immediate access or a free plan.