Assertion Labs / Advisory

Make consequential decisions reconstructable.

Design evidence lineage and decision records so a team can explain which source, policy and approval supported an action, and what changed afterward.

Discuss an evidence workflow →

Context

Engineering and security teams whose automated workflows cannot reliably reconstruct a decision or distinguish current evidence from superseded material.

Preparation & access

A workflow diagram, representative redacted decision logs, source-version conventions and retention requirements. Share only authorized artifacts through an agreed channel after scoping.

Work & deliverables

  • An inventory of evidence sources and lineage gaps
  • A proposed decision-record schema and retention boundaries
  • A bounded instrumentation prototype or implementation plan, as agreed
  • Verification scenarios for changed, missing and contradictory evidence

Scope & limitations

Implementation is limited to the agreed workflow. No compliance attestation, legal retention advice or guarantee of complete historical reconstruction. CliqueMap use is evaluated separately; it is not a prerequisite.

Offered subject to fit, conflict review and availability. A conversation is not acceptance of an engagement.

Related writing and research →

How we work

Begin with a bounded question.

  1. Define the decision, boundaries, conflicts and available evidence.
  2. Agree on the work, deliverables, access and review process.
  3. Examine claims and record findings with their limitations.
  4. Discuss implications and the next decision.