Founder
Ishaan Ghosh
Ishaan Ghosh is the founder of Shango MID, a write-governance and memory-custody layer for AI agents writing to systems of record. He is the sole author of the architecture and the accountable party for every claim made about it.
What Shango MID does
Decides before the action
A proposed write is checked against declared authority and scope before it takes effect — allowed, blocked, or returned to a person.
Evidences in the same breath
The receipt is committed inside the same database transaction as the decision. If the receipt cannot be written, the transaction rolls back and the caller gets a refusal.
Leaves something checkable
A log vouches for itself. A receipt an outsider can check against a published key is a different kind of object.
Counter-signing is not running in the current build
The design provides for each receipt to be counter-signed by a separate legal entity, so the record can be checked without trusting Shango. That signing path was exercised across thirteen completed runs in 2026, and those receipts remain independently verifiable against the attester's published key. It is not running today — receipts are committed, not counter-signed.
The published record
What it does, and what it does not.
There are more things declared here that Shango MID cannot do than things it can. That is deliberate. A control you cannot inspect the limits of isn't a control — it's a reassurance.
What it does
- Decides whether an automated write is permitted before it happens
- Commits the receipt inside the same database transaction as the decision
- Rolls the decision back if the receipt cannot be written
- Detects alteration of a committed receipt via the hash chain
- Produces receipts a third party can verify offline against a published key
What it does not establish
- Prove that nothing happened outside the governed path
- Establish that a permitted action actually occurred
- Verify the acting agent's identity — the actor is the caller's assertion
- Counter-sign receipts in the current build — that is not running
- Hold any certification, accreditation or conformity assessment
Eleven limitations in total, filed in full on a public registry record. Shango MID is pre-revenue: no customers, no delivered engagements, no third-party production deployments.
400 permitted, 600 blocked. Counter-signed and verifiable offline against a published key.
The authorisation-context run. Two 500-receipt runs exist, so the date is the identifier.
Of the 14: nine borne by shipped code, four by test scaffolding, one with no mechanism.
Every figure traces to one of these
Not independently recomputed — the conformance runner is closed.
With Tim Zlomke. A specification arrived at by argument; neither author has implemented it.
Greg Malpass, Constitutional Memory Governance (2026).
Registration is not certification and verifies none of these claims.
Defects found in this architecture are published with the name of the reviewer who found each one, including the ones that were ours. Check it yourself.
What he built
Ishaan Ghosh designed and built Shango MID: the enforcement engine, the four-verdict decision lattice, the effect-binding and aggregate-exposure controls, and the offline verifier that lets anyone check a published receipt against the attester's public key. The conformance runner itself is closed and is not published.
A risk register for the architecture is published with a residual column rather than a mitigation column. Sixteen risks; eight do not yield to engineering effort, and three require a second party by construction.