Evidence explains what was submitted.
Decision logs explain what the system did with it.
Launch accountability requires records of artifacts, the decisions made using them, and the changes that followed.
The Evidence Graph needs two related records: DecisionLog and ChangeLog.
DecisionLog records who decided what, on what evidence, and why. ChangeLog records what changed, when it changed, who approved it, and what version became effective.
Connecting artifacts to decisions
A venture can submit a document and still leave stakeholders with unanswered questions.
Was the document reviewed? Who reviewed it? Was it accepted, rejected, or sent back for remediation? Which standard did it satisfy? Was the decision automatic or manual? Did anyone attach conditions to the approval?
Decision records explain how the submitted evidence affected the evaluation and applicable workflow.
DecisionLog closes that gap.
What a DecisionLog should capture
A DecisionLog records the decision context.
At minimum, it should capture the decision made, the gate or standard involved, the evidence referenced, the reviewer or system actor, the rationale where applicable, the timestamp, and the resulting system effect.
For example, an audit-status review should show the audit evidence, reviewer, outcome, and open remediation. SA-02 is Advised in the standards registry, so its status must retain that enforcement class.
That makes the gate outcome inspectable later.
Why rationale matters
Not every decision can be reduced to a yes or no.
Some evidence requires judgment. Some remediation is accepted with conditions. Some standards trigger review because context matters. In those cases, rationale is part of accountability.
A short rationale can prevent future confusion. It tells later reviewers and stakeholders why the decision was made at the time and which evidence supported it.
That is especially important in post-launch disputes, regulatory inquiry, and standards review.
What a ChangeLog should capture
A ChangeLog records evolution.
It should capture what changed, the prior state, the new state, the reason for change, the approving actor, the effective date, and the related evidence or decision.
This applies to artifacts, standards, policies, disclosures, governance settings, and material venture updates. If a venture changes its allocation register, there should be a record. If a standard changes version, there should be a record. If remediation updates the status of a finding, there should be a record.
Change is normal. Unrecorded change is the risk.
How DecisionLog and ChangeLog work together
DecisionLog and ChangeLog answer different questions.
DecisionLog asks: what decision was made, on what evidence, and by whom?
ChangeLog asks: what changed afterward, why, and under whose authority?
Together, they create a timeline. Evidence enters the system. A decision is made. A change may follow. That change becomes part of future context. The lifecycle remains traceable across the snapshots.
Why investors should care
Investors need to understand the venture’s current state and the decisions that produced it.
A venture that changed its governance model after launch may still be credible. A venture that updated remediation after an audit may still be improving. A venture that revised disclosures may be acting responsibly. The key is whether those changes are logged, explained, and attributable.
DecisionLog and ChangeLog make change evaluable.
What stakeholders should look for
Stakeholders should ask whether platform history is reconstructable.
- Can the platform show who approved a gate?
- Can it show what evidence supported the decision?
- Can it show the rationale for manual review outcomes?
- Can it show what changed after approval?
- Can it show which version was effective at the time?
These answers show the scope and quality of the recorded accountability.
Launch accountability depends on records.
DecisionLog records who decided what and why.
ChangeLog records what changed afterward.
Together, they turn evidence into an auditable lifecycle.
That is how decisions become traceable.
That is how change becomes accountable.
This is how we Become Alpha.