For general counsel

Defensible governance before the regulator asks.

You’re the one who has to defend governance decisions after the fact. When a regulator, court, or board asks “what governance was in place?”, you need contemporaneous evidence — not post-hoc narratives reconstructed from email chains and meeting minutes. The difference between a defensible position and personal liability is whether the governance record demonstrates what you knew and what you did, at the time it happened.

The problem

Governance evidence is constructed retrospectively. When something goes wrong, legal teams reconstruct the narrative from email threads, Slack messages, meeting minutes, and individual recollections. The problem isn’t that governance didn’t happen — it’s that the evidence of governance wasn’t captured at the moment of action. You’re building a defence from memory, not from records.

This gap is existential for General Counsel. You are personally accountable for the adequacy of governance infrastructure. If AI agents are making decisions without governance constraints, if delegations aren’t recorded, if escalations happen informally — the absence of evidence becomes evidence of absence. And courts are now explicit about that standard.

Post-hoc
Evidence reconstructed after failure
Personal
CLO liability now established
Invisible
AI agent decisions without governance

Legal standard — ASIC v Bekier [2026] FCA 196

The Chief Legal Officer was held personally liable alongside the CEO. The court’s standard was unambiguous: contemporaneous records, not post-hoc explanations. The court reconstructed three things — who was responsible, what they knew, and what they did — and found the governance record insufficient. For General Counsel, this is existential: if your governance infrastructure doesn’t produce evidence at the moment of action, you’re building your defence from memory.

Full analysis: CLO liability and the three-question standard

How Constellation solves it

Governance evidence produced at the moment of action

Constellation doesn’t log governance after the fact. It captures governance as it happens. Every constraint check, every escalation, every delegation, every override — recorded immutably at the moment of action. The evidence package exists before anyone asks for it.

Contemporaneous evidence

Every governance event — constraint check, escalation, delegation, override — creates an immutable governance trace at the moment it happens. Not logged after. Captured during.

Three-question readiness

At any moment, Constellation can answer: who was responsible (delegation chain via progressive delegation), what did they know (information available at the decision point), and what did they do (action taken, constraint applied). This is the ASIC v Bekier standard, built into infrastructure.

Contestation layer

Structured disagreement through the Forum. Challenges, evidence, rulings, precedent. When someone disagrees with a governance decision, the disagreement itself is governed — creating a record of institutional reasoning that demonstrates due process, not just outcomes.

Regulatory export

Governance telemetry exportable as PDF/CSV for regulators, auditors, and courts. The Governance Confidence Index provides a quantified measure of governance health. The evidence package exists before anyone asks for it.

What changes

Instant
Evidence at point of action
Defensible
Three-question readiness
Structured
Contestation + precedent
Complete
Governance telemetry export

You stop reconstructing governance narratives and start producing them automatically. Every governance event is evidenced at the moment it occurs. When a regulator, court, or board asks what governance was in place, the answer is already assembled — contemporaneous, complete, and exportable.

Key concepts

Defence-ready governance infrastructure

You’re personally accountable for governance adequacy. Constellation ensures the evidence exists before anyone asks for it — contemporaneous, structured, and exportable.