Public proof ledger

Trust comes from artifacts, not adjectives.

Unwind Code turns the build process into evidence: transmissions, whitepapers, architecture decisions, safety gates, and status labels that make the organism ecosystem inspectable.

Read archive→ Study architecture
Evidence register

Start with public artifacts, then inspect the boundary they prove.

Each row answers a trust question: what exists, what it proves, what risk boundary it supports, and where to inspect the source.

7 public artifacts
5 authority boundaries
3 status classes
Transmission 27
Transaction readiness

The Quotation Cell

Turns quoting into a governed packet: supplier evidence, correction memory, readiness state, and approval before commitment.

Status
Public
Proves
Commercial action can stay reviewable before a human commits.
Open Transmission 26
Bounded sales cell

The Property Sales Intelligence Cell

Shows permitted-source review, intent qualification, evidence preservation, compliance posture, and human approval before outreach.

Status
Public
Proves
Agentic sales work can be bounded before external motion.
Open Transmission 25
Interface proof

The Homepage Learned to Pulse

Documents the organism-pulse hero, semantic asset governance, proof metadata, and post-ready social packet.

Status
Public
Proves
The homepage claim is backed by schema, manifest, tests, and shareable release assets.
Open Transmission 21
Whitepaper

The Unwind Brain Whitepaper

Defines the Brain as a human-governed cognitive organism: memory, approvals, public proof, Web3 safety, and bounded cell growth.

Status
Public
Proves
The organism architecture has a written operating model.
Open Transmission 22
Financial safety

The Monad Hand

Shows why the Financial Survival Organism chooses clarity before financial motion.

Status
Public
Proves
Money decisions start with interpretation, not transaction authority.
Open Transmission 23
Safety gate

The SEC Gate

Explains how an organism can lock its own hands before unsafe execution.

Status
Public
Proves
High-risk action belongs behind refusal, review, and approval gates.
Open Transmission 24
Product form

The Mirror Found Its Form

Documents the Infinity Mirror product grammar and why the user-facing organism is not another dashboard.

Status
Public
Proves
Human-facing organisms need product clarity before more controls.
Open
Trust diligence console

Different visitors inspect different proof before they trust the organism.

The ledger now routes due diligence by intent. Choose the visitor lens, then inspect the evidence, authority boundary, and next route that should come before conviction.

Read transmissions Start a proof packet
Choose a diligence lens
Architecture proof

A builder should see how the system is assembled before touching tools.

Evidence path
Architecture map, Brain Cell lifecycle, runtime console, and whitepaper transmission.
Boundary
Generated cells stay inert until tests, sandbox evidence, review, and approval pass.
Status proof

An investor should see status, proof gaps, and restraint before conviction.

Evidence path
Seven public artifacts, social proof packets, status labels, metadata, and explicit authority gates.
Boundary
No financial promises, hidden metrics, private deal claims, or live Web3 authority are implied.
Product proof

A user should know what is safe to try and what the organism will not decide.

Evidence path
Infinity Mirror product form, session console, reflection loop, prototype status, and human boundary copy.
Boundary
No diagnosis, care decision, identity judgment, or life choice is outsourced to automation.
Web3 proof

A protocol should inspect how on-chain intelligence stops before money motion.

Evidence path
Web3 trust-layer map, simulation console, Monad Hand, SEC Gate, and unsigned packet posture.
Boundary
No private keys, no hidden wallet path, no live money motion, and no broadcast by default.
Sprint proof

A collaborator should see the first sprint proof before work begins.

Evidence path
Collaboration packet, engagement fit, authority boundary, expected artifact, and first useful proof.
Boundary
No engagement starts without domain, owner, risk edge, review path, and public-safe proof bar.
Asset governance ledger

The visuals are governed proof surfaces, not decoration.

Every immersive asset has to explain architecture, clarify trust, guide a route, or make an authority boundary inspectable. The manifest records why it exists and how it behaves.

Open asset manifest Build a proofed asset
Purpose filter

Every visual must earn its place.

Assets explain the organism ecosystem, clarify architecture, build trust, route visitors, or expose proof.

Text boundary

Meaning stays inspectable outside the image.

Critical labels and claims live in HTML, translations, schema, tests, llms.txt, ai-services.json, and the manifest.

Motion policy

Immersion stays lightweight and respectful.

SVG and CSS motion come first, reduced-motion users get static proof, and heavy 3D never blocks comprehension.

Discovery trail

Crawlers and future agents can find the asset contract.

The build copies the asset, manifest, llms.txt, ai-services.json, and sitemap so the public proof trail survives deployment.

Verification loop

A claim is not trusted until it leaves a trail.

The proof loop is the public face of governance: claims become artifacts, artifacts name boundaries, and boundaries point to reviewable evidence.

  1. 01

    Claim

    State what the organism can do without inflating autonomy.

  2. 02

    Artifact

    Link the claim to a transmission, architecture note, test, or release packet.

  3. 03

    Boundary

    Name what the system cannot do without human authority.

  4. 04

    Review

    Make sandbox, safety, and status evidence readable before action.

  5. 05

    Memory

    Preserve the lesson so the next organism run starts sharper.

Safety boundaries that visitors can understand.

The public story stays credible because the site names where autonomy stops.

01

Generated code

Runs in sandbox before integration.

02

Filesystem

Writes are explicit and reviewable.

03

Money

Financial motion requires proof and human approval.

04

Public posts

External publishing needs a reviewed packet.

05

Status labels

Prototype, research, and live claims stay separate.

Authority gate console

The organism must prove why it should act before it receives authority.

Generated capability is useful only when visitors can see the stop signs. This console turns each high-risk action into a request, immune response, evidence trail, and human authority boundary.

Read the SEC Gate Design an approval path
Choose a high-risk action
Sandbox

Generated code stays quarantined until it proves itself.

Request
A new cell, patch, or self-evolution proposal wants source access.
Immune response
Run in sandbox, test the behavior, and deny host authority by default.
Evidence
Diff, tests, sandbox result, rollback note, and proof artifact.
Human authority
A creator approves integration before the organism can load the capability.
Review

Filesystem writes become scoped, reversible review packets.

Request
The organism wants to create, edit, delete, or reorganize files.
Immune response
Expose the exact path, diff, ownership boundary, and rollback route.
Evidence
Patch preview, affected routes, tests, and filesystem truth docs.
Human authority
Only scoped, reviewable writes cross the gate; destructive host actions pause.
Approval

Financial motion starts as interpretation, never silent execution.

Request
A financial organism identifies a bill, opportunity, debt move, or risk.
Immune response
Simulate, classify risk, explain tradeoffs, and keep transaction authority closed.
Evidence
Scenario packet, assumptions, constraints, and approval checklist.
Human authority
Money moves only after explicit operator consent.
Publish packet

Public output waits for a reviewed publishing packet.

Request
The organism wants to publish a post, transmission, release note, or public reply.
Immune response
Draft, cite sources, name claims, and separate private reasoning from public language.
Evidence
Preview copy, destination, proof links, status label, and reviewer decision.
Human authority
No external post leaves the lab without a human publish decision.
No broadcast

On-chain intelligence stays read-only until authority is explicit.

Request
A Web3 workflow asks for wallet context, signing, or transaction broadcast.
Immune response
Use read-only data, simulate outcomes, and produce unsigned packets only.
Evidence
Risk score, unsigned transaction shape, chain assumptions, and no-private-key proof.
Human authority
Broadcast remains locked by default; signing never hides inside the organism.
Use the ledger

Need an organism people can trust before it acts?

Bring a goal, an authority boundary, and the proof your audience would need. The lab can turn it into an architecture review, prototype organism, or proof-loop audit.

Build with proof→ Explore organisms