Record what changed and what you can demonstrate
Approval does not prove execution, and a log does not by itself establish a complete history. Organise events with evidence and limits. Think² supports groups, context, the option for each collaborator to have its own computer, compatible models and authorised tools; those capabilities are not audit certification or a guarantee of complete, tamper-proof records.
Waitlist: no guaranteed immediate access or free plan. The destination is in Spanish.
Situations to review
An approved proposal is treated as an executed change
Record the proposal, approval, attempt and verification as separate events, linked by correlation references and specific evidence for each status.
An approval is not proof that the destination received or applied the change. An unknown outcome remains unknown until sufficient evidence is available.
A log contains sensitive data and appears to retain everything
Define its purpose, minimum fields, access permissions, known coverage and authorised retention. Exclude secrets and unnecessary personal information and record systems or periods outside its coverage.
The record serves a defined review without promising total surveillance, complete memory or compliance through retention alone. Do not log private step-by-step reasoning.
A hash is added and the log is described as immutable
Distinguish a calculated fingerprint from an integrity mechanism with a protected reference and verified controls. If both the data and hash can be rewritten, the isolated hash does not detect that replacement.
A hash column does not establish integrity, authorship, completeness or certification. Signatures, append-only storage and access controls need their own implementation and tests.
Waitlist: no guaranteed immediate access or free plan. The destination is in Spanish.
How to evaluate the work
- Define the event and its purpose. Separate the object, previous version, proposal, approval reference for every external action, and what was actually observed afterwards. A logged status needs evidence proportionate to its claim; qualify what verified means. Every external action requires prior, specific approval for that action and its scope.
- Record when, where, who and what: event and log-entry times with timezones, source, object identifier, action, result and correlation. An actor field helps review an attribution but is not proof of real-world identity. Record verifiable sources and decisions, not private internal reasoning.
- Set limits on access, retention and protection. Do not copy passwords, tokens or unnecessary personal data. An authorised policy must account for purpose and applicable requirements, without an invented universal period. Verify coverage, gaps, clock synchronisation and tamper controls; using this template does not prove those controls exist in Think² or another system.
Reusable template: event ID; occurrence date/time/timezone; log-entry date/time/timezone; actor/source; object/previous version; proposal; observed state/version; correlation; purpose; action/status; evidence; external approval reference; retention policy; coverage/gaps.
Fictional example, not a real run: DOC7 version3, proposed version4, approvalA19 and requestRQ88 under correlationCORR51. Event1: proposal at14:10UTC; event2: approval at14:11UTC; event3: attempt at14:12UTC, timeout and unknown outcome. Event4: query at14:15UTC, when the fictional destination reports version4 and referenceRQ88. Record verification of that state and reference at that cutoff, without inferring real authorship or the integrity of the whole history. If the destination showed version4 without the request reference, that would not establish that this attempt caused the change. Times are illustrative, not actual measurements; retention is unspecified. No Think² integration or execution occurred. Approval is not execution, and checking a state does not authorise repeating the action.
Process log and source history: compare coverage, not labels. They are not automatic substitutes. A process log may record proposal, approval and attempt; source history may supply the version and outcome that system exposes. Neither establishes the whole sequence or greater integrity by itself. Before choosing or combining them, compare events, fields, cutoffs, attributed actor, correlation, timezones, access, retention and tamper controls. A missing event may be a coverage gap, not evidence that it never occurred. Two matching records are not independent evidence if one derives from the other.
Object/version; required event; process log/field/evidence; source history/field/evidence; origin or derivation; occurrence and entry time/timezone; correlation; verified or pending coverage; access; retention policy; tamper protection; contradiction and next check.
Fictional example extending DOC7/RQ88 without adding a run: the log describes an attempt at14:12UTC with an unknown outcome; the fictional source reports version4 at14:15UTC. If it does not expose RQ88, that state does not establish that the attempt produced the version. If it exposes that reference, record the scope of that correlation at the cutoff, not the actor's real identity or complete integrity. Retention and controls have not been checked: leave them pending. No real histories were queried and no advantage of one log over another was demonstrated. OWASP distinguishes application and infrastructure logging and recommends protection and verification; it does not say a process log outperforms every source history.
This is not proof of Think² integrity, retention, coverage or append-only storage. Retain only necessary data, never secrets or private reasoning. Every external action needs prior specific approval; an approval record does not establish execution.
Frequently asked questions
Does a change log prove who made a change?
Only what its records and evidence support. Actor, source and request references help attribute events but do not certify real-world identity or the integrity of the history.
Does a hash make the history immutable?
Not by itself. If the log and hash can both be changed, that isolated fingerprint does not establish that earlier content remained intact. Protected references, signatures or append-only storage require concrete, verified controls.
How long should records be retained?
It depends on the purpose, applicable requirements and authorised policy. Define retention, access and coverage with the responsible people and document gaps. This example establishes no legal period or compliance certification.
Sources and scope
- OWASP — Logging Cheat Sheet — Events, when/where/who/what, correlation, excluding secrets, protection and retention. Not implementation certification.
- W3C — PROV-O — Provenance entities, activities and agents, not proof of complete or tamper-proof logs.
Keep exploring
- Control access and company data (Spanish)
- Organise administrative processes (Spanish)
- Approve external actions (Spanish)
- A computer each collaborator can have (Spanish)
Waitlist: no guaranteed immediate access or free plan. The destination is in Spanish.