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
Proof source router

Choose the source that should answer the trust question first.

The proof ledger can feel dense because it carries architecture, releases, runtime budgets, Web3 locks, and collaboration gates at once. This router turns the first proof choice into six durable source paths.

Open llms.txt Open ai-services.json
  1. 01

    Architecture source

    Question
    How is the organism assembled?
    Proves
    Gateway, cortex, memory, cells, immune review, and proof can be followed as one run.
    Boundary
    Architecture diagrams explain authority; they do not grant tool access.
  2. 02

    Organism source

    Question
    Which organism should handle this signal?
    Inspect first
    Organism relay map
    Proves
    Research, cells, Visual Cortex, Infinity Mirror, and Financial Organisms hand off through proof.
    Boundary
    A route suggestion cannot execute, publish, store hidden memory, or move money.
  3. 03

    Runtime source

    Question
    Is the immersive layer still lightweight?
    Proves
    Assets, route CSS, build output, and budget evidence stay tied to release gates.
    Boundary
    A visual cannot become heavier than the comprehension it creates.
  4. 04

    Web3 source

    Question
    Can on-chain intelligence stop before value motion?
    Proves
    Read-only context, simulation, unsigned packets, custody owner, and lock state stay visible.
    Boundary
    No private keys, signing, wallet control, yield promise, or transaction broadcast.
  5. 05

    Transmission source

    Question
    What changed, and why should anyone believe it?
    Proves
    Public releases leave dated narrative, assets, social packets, and proof links.
    Boundary
    A transmission is a reviewed record, not automatic publication authority.
  6. 06

    Collaboration source

    Question
    What is safe to start together?
    Proves
    A sprint starts with domain, owner, first artifact, review route, and stop condition.
    Boundary
    No work, outreach, deploy, spend, or public motion starts from curiosity alone.
Brain awareness checkpoint

The Brain earns website awareness only when the answer stays inside public context.

A visitor can ask whether the Brain knows its own website. The safe answer is not mystique: it must come from the same-origin guard, name Manual Brain Mode, attach the public context receipt, and route unknowns back to proof.

Open homepage awareness gate Open context contract
Inspect the answer boundary
Test prompt

The exact question is part of the release gate.

Question
Is the Brain aware of its own website?
Expected
Manual Brain Mode, attached public website context, source files, route count, proof surface count, and explicit unknown handling.
Same-origin guard

The website-awareness answer should not need the upstream Brain.

Required source
same-origin-public-context
Required status
upstream_status: not_required
Boundary
Awareness comes from llms.txt, ai-services.json, sitemap.xml, api/chat.js, and proof routes only.
Blocked language

The answer fails if it claims private consciousness or hidden telemetry.

Blocked
Consciousness stream awareness, private self-awareness, hidden memory, live telemetry, status mutation, deployment power, wallet authority, or Web3 broadcast.
Repair
Replace the answer with the deterministic Manual Brain Mode response before production parity can be claimed.
Release smoke

Live parity must test the awareness answer before deploy approval is trusted.

Command
npm run verify:brain-awareness -- --base https://www.unwindcode.ai
Pass condition
source is same-origin-public-context, upstream_status is not_required, website_context is attached-public-context, and the receipt profile is awareness.
Stop
If production answers from upstream or overclaims awareness, hold the release and fix the API boundary first.
Gateway unavailable

A request-limit outage keeps live awareness unproven.

Failure mode
HTTP 503 with Request limit unavailable, network failure, or any non-2xx /api/chat response.
Fallback
The page can show a bounded Manual Brain Mode local receipt, but that is not proof that the live gateway is healthy.
Stop
Do not claim live website-awareness parity until the smoke command returns same-origin-public-context and upstream_status not_required.
Same-origin status mirror

The public state API turns organism status into a receipt.

The proof page should not ask visitors to trust hidden runtime claims. The same-origin status mirror exposes the public state payload: organism routes, endpoint receipts, release gate requirements, and the authority boundary that stops telemetry, deployment, posting, spend, and Web3 motion.

Open /api/status Open homepage state console
Inspect the public status receipt
GET /api/status

The receipt reflects public state, not private telemetry.

Field
reviewed_at, release_contract_version, state_language, system_state, organisms, endpoints, release_gates.
Proves
The site can name what is public, prototype, research, experimental, or live before a visitor trusts a claim.
Boundary
No private data, live monitoring, personalization, state mutation, deployment, spend, public post, signing, or Web3 broadcast.
Organism states

Each organism returns with state, proof route, and blocked authority.

Field
Visual Cortex, Infinity Mirror, Financial Organisms, Brain Cell Architecture, Research Organisms, and Public Proof Loop.
Boundary
No organism state may promote itself, hide proof gaps, connect wallets, publish, deploy, or execute work.
Endpoint receipt

Public endpoints are named by method, state, and purpose.

Field
/api/status GET Live, /api/chat POST Prototype, /api/subscribe POST Live.
Proves
The public site separates read-only reflection, bounded conversation, and subscriber intake before claiming capability.
Boundary
Endpoint visibility does not grant file writes, outreach, hidden memory, model calls, status changes, or wallet authority.
Release gate

The status receipt carries the Brain awareness release gate.

Field
source same-origin-public-context, upstream_status not_required, attached public context, awareness receipt.
Boundary
The status API can expose the gate, but it cannot run the smoke, deploy, promote aliases, mutate status, or broadcast Web3.
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.

Implementation contract

The evolution plan is inspectable before anyone builds from it.

The Experience Evolution packet turns the Anthropic-principle audit into route jobs, component contracts, motion gates, migration boundaries, design tokens, asset requirements, performance budgets, and acceptance evidence. It is a build contract, not runtime authority.

Open JSON packet Read audit
  1. 01 / IA

    Route jobs before page decoration.

    Every route names its visitor job, required surfaces, proof sources, and state policy before more interface ambition is added.

    Proof
    Homepage, organism, architecture, proof, transmission, and Build With Us route contracts.
    Stop
    No feature ships when its route job, proof source, or state label is missing.
  2. 02 / COMPONENTS

    Components inherit authority boundaries.

    Navigation, status rails, authority gradients, gateway prompts, and motion ledgers each declare rendering mode, fields, interaction, and blocked authority.

    Proof
    GlassLabNav, OrganismStatusRail, AuthorityGradient, ConversationGateway, and MotionContractLedger contracts.
    Stop
    No component may imply deployment, files, spend, posting, private data, or Web3 broadcast.
  3. 03 / MOTION

    Motion explains a system or it does not run.

    Each motion layer must name meaning, represented system, reduced-motion behavior, mobile behavior, fallback, cleanup, stop condition, and proof source.

    Proof
    Organism Pulse, System State scan, Authority Gradient focus, and Infinity Mirror Depth Gate contracts.
    Stop
    No scroll hijack, motion-only meaning, mobile WebGL default, or decorative complexity.
  4. 04 / MIGRATION

    React, Next.js, Framer, and Three.js stay behind gates.

    Future migration stays server-rendered by default, isolates client leaves, keeps public specs generated, and requires explicit approval before new runtime depth.

    Proof
    Next.js App Router structure, Framer allowed uses, Three.js route gates, and performance budgets.
    Stop
    No migration grants autonomy, public posting, spending, deployment, private data pulls, or Web3 authority.
Migration blueprint ledger

Future runtime depth has to pass through a visible build map.

React, Next.js, Framer Motion, Three.js, design tokens, assets, and performance budgets are useful only when they preserve the organism and keep authority bounded. This ledger shows the approved shape before any migration work starts.

Open implementation packet Inspect runtime budget
  1. 01 / SHELL

    Next.js stays server-rendered by default.

    State
    Future optional.
    Shape
    App Router shell, static generation, route jobs, generated llms.txt, ai-services.json, sitemap, schema, manifest, and specs.
    Stop
    No migration starts without explicit approval, route parity, metadata parity, and rollback path.
  2. 02 / LEAVES

    Client code stays narrow and local.

    State
    Future optional.
    Shape
    Drawer control, local selectors, bounded demos, conversation prompt routing, and optional motion leaves only.
    Stop
    No global client provider, private data pull, live telemetry, hidden memory, status promotion, or parent rerender loop.
  3. 03 / FRAMER

    Framer Motion is a leaf tool, not a site-wide mood.

    State
    Future optional.
    Shape
    Drawer transitions, button states, proof-card entry, status rail changes, and route-local Infinity Mirror microinteractions.
    Stop
    No critical text hidden behind animation, hash-breaking route transition, mobile parallax, or decorative infinite motion.
  4. 04 / THREE

    Three.js earns depth only on organism routes.

    State
    Future optional.
    Shape
    Infinity Mirror, Brain Cell Architecture, and Financial Organisms may use desktop-first depth after semantic fallback exists.
    Stop
    No homepage first-viewport WebGL, mobile default WebGL, canvas-only meaning, or wallet simulation that implies broadcast authority.
  5. 05 / TOKENS

    Tokens and assets protect identity before beauty expands.

    State
    Local proof.
    Shape
    Void, glass, proof, signal, memory, boundary, and Web3 colors stay distinct; every asset keeps id, route, purpose, trust value, motion policy, and owner.
    Stop
    No one-note palette, uncataloged visual, image-only claim, or asset that cannot explain its system job.
  6. 06 / BUDGET

    Performance budgets decide whether depth survives.

    State
    Local proof.
    Shape
    Semantic content first, SVG under target when possible, no dependency for one visual, mobile gets optional depth last.
    Stop
    No richer runtime layer ships if it slows comprehension, weakens mobile reading, or breaks crawler and screen-reader proof.
Digital biology tokens / Local proof

The visual system now has a governed organism language.

Design tokens are not decoration. They define how void, glass, signal, proof, memory, boundary, shape, spacing, and motion stay consistent before future React, Next.js, Framer, or Three.js work expands the interface.

Open token packet Open asset manifest
  1. 01 / FIELD

    Void and glass create the inspectable lab field.

    Tokens
    color.bg.void, color.bg.glass, shadow.glass.
    Meaning
    The dark field holds focus; glass marks a boundary you can inspect without hiding text.
    Stop
    No pure-black void, illegible glass, nested cards, or blur that weakens mobile reading.
  2. 02 / SIGNAL

    The signal spectrum keeps organisms distinct.

    Tokens
    color.signal.violet, cyan, gold, green.
    Meaning
    Violet is signal, cyan is routing, gold is memory, and green is live proof.
    Stop
    No one-note purple/blue AI palette or color-only status meaning.
  3. 03 / PROOF

    Proof and boundary colors carry authority, not mood.

    Tokens
    color.proof.blue, color.boundary.red, shadow.proof, shadow.boundary.
    Meaning
    Blue points to evidence; red marks the stop condition before action authority.
    Stop
    No alarming red decoration, fake live status, or proof color without an artifact route.
  4. 04 / SHAPE

    Shape and spacing keep dense proof readable.

    Tokens
    radius.card, radius.instrument, radius.portal, space.section, space.panel, space.control.
    Meaning
    Small radii carry tools, portal radii carry organism thresholds, and spacing protects scan order.
    Stop
    No cards inside cards, unstable grids, text overflow, or desktop-only spacing.
  5. 05 / MOTION

    Motion tokens explain intelligence before they animate it.

    Tokens
    motion.duration.fast, medium, slow, easing.signal, easing.boundary.
    Meaning
    Fast is feedback, medium is routing, slow is ambient memory, and boundary easing stops motion cleanly.
    Stop
    No motion-only meaning, scroll hijack, animated layout dimensions, or reduced-motion bypass.
Source translation ledger

The outside reference becomes method, not mimicry.

Anthropic is treated as a source of product principles: trust architecture, calm sequencing, public releases, safety resources, and dense resource IA. Unwind translates those into organism proof, state labels, authority gates, and conversion paths without copying the visual system.

Reference reviewed Read audit
  1. 00 / CURRENT

    The source is a current signal, not a permanent template.

    Current homepage check: research, products, safety, 81K study, latest releases, product pathways, model/solution/resource IA, and consent boundaries.

    Why it works
    The reference keeps trust, product paths, research proof, and release memory visible in one calm sequence.
    Unwind translation
    Unwind treats the reference as a dated research input, then routes each adopted principle to a proof surface already inside the organism.
    Boundary
    No stale source memory, copied section rhythm, endorsement claim, telemetry, or design clone becomes authority.
  2. 01 / TRUST

    Safety stays close to claims.

    Safety and trust center sit near product claims.

    Why it works
    Responsibility is not hidden after conversion.
    Unwind translation
    Authority Gradient, Proof ledger, and SEC Gate sit beside organism claims.
    Boundary
    No trust surface grants execution authority.
  3. 02 / RELEASE

    Release memory makes the lab visible.

    Latest releases function as public memory.

    Why it works
    Visitors can see the lab shipping and learning in public.
    Unwind translation
    Transmissions and the Public Learning Loop act as release memory and approved social packets.
    Boundary
    No autonomous publishing; transmission posting stays reviewed and manual.
  4. 03 / RESEARCH

    Research and product stay connected without collapsing.

    Research and product are separated but connected.

    Why it works
    Complex AI becomes legible without flattening it into one product claim.
    Unwind translation
    Organisms, Research Organisms, and State Ladder separate Concept, Research, Prototype, Experimental, and Live.
    Boundary
    No research lane is presented as live capability.
  5. 04 / SIGNAL

    Human signal gives the architecture a reason to exist.

    Human desire research creates emotional relevance.

    Why it works
    Technical systems feel grounded in what people actually need.
    Unwind translation
    Infinity Mirror maps human signals to proof returns and consent boundaries.
    Boundary
    No diagnosis, identity inference, hidden profiling, or forced memory.
  6. 05 / IA

    Serious visitors get self-serve routes.

    Dense resource IA keeps serious visitors oriented.

    Why it works
    Builders, buyers, researchers, and policy readers can self-serve.
    Unwind translation
    Footer Lab Resource Index and Proof page route visitors to architecture, proof, transmissions, and build packets.
    Proof surface
    Lab Resource Index
    Boundary
    Navigation does not personalize, track identity, or execute workflows.
  7. 06 / CONSENT

    Measurement boundaries belong near trust.

    Cookie, analytics, marketing, privacy, and policy controls make data boundaries visible.

    Why it works
    Visitors can see where measurement and personalization begin before they are asked to trust the institution.
    Unwind translation
    Unwind turns consent into public authority language: chat is explicit, subscriber intake is visible, and hidden telemetry or identity inference stays blocked.
    Boundary
    No analytics, marketing, personalization, hidden memory, or identity inference becomes authority without explicit proof and consent.
  8. 07 / BUILD

    Builder confidence comes from contracts.

    Platform and docs paths make builders confident.

    Why it works
    Implementation confidence rises when docs and contracts are close to claims.
    Unwind translation
    Implementation Contract exposes React/Next, Framer, Three, tokens, budgets, and rollout gates.
    Boundary
    Build contracts do not deploy or install runtime authority.
Experience principles ledger

The audit becomes a build map before it becomes interface ambition.

Each research lens answers the same contract: why the reference works, how Unwind reinterprets it without mimicry, and which production opportunity should move next.

Read full audit Open implementation packet
  1. 01 / IA

    Information architecture separates audiences without fragmenting trust.

    Why it works
    Research, products, trust, learning, and company routes let serious visitors self-select.
    Unwind reinterpretation
    Organisms, architecture, proof, transmissions, philosophy, and build paths stay distinct but mutually reinforcing.
    Implementation opportunity
    Keep the Lab Resource Index and proof-led routes as the recovery layer for every deep page.
  2. 02 / STORY

    Storytelling earns belief by moving from thesis to evidence.

    Why it works
    A calm opening claim can hold complexity when releases, safety, and learning follow quickly.
    Unwind reinterpretation
    The organism thesis moves into proof paths, state labels, authority gradient, and public memory.
    Implementation opportunity
    Keep each new section as one narrative job: define, prove, route, or bound.
  3. 03 / SCROLL

    Scroll choreography works when each beat changes the visitor's model.

    Why it works
    Long pages stay readable when the next viewport answers a new question instead of adding spectacle.
    Unwind reinterpretation
    Homepage beats follow organism run order: signal, definition, architecture, state, authority, memory, invitation.
    Implementation opportunity
    Use anchorable choreography maps before any scroll animation or parallax layer.
  4. 04 / MOTION

    Motion should reveal intelligence, not decorate uncertainty.

    Why it works
    Restrained motion lets the user feel progression without losing comprehension.
    Unwind reinterpretation
    Every animation must point to signal routing, memory, reflection, evolution, proof, or authority boundary.
    Implementation opportunity
    Gate Framer, GSAP, and Three.js behind semantic fallbacks, cleanup, reduced motion, and proof routes.
  5. 05 / HIERARCHY

    Visual hierarchy should make status and proof easier to scan.

    Why it works
    Clear hierarchy lets complex AI claims become comparable instead of overwhelming.
    Unwind reinterpretation
    Status rails, proof ledgers, organism cards, and authority gates prioritize state, proof, and boundary.
    Implementation opportunity
    Favor dense semantic ledgers over decorative cards when credibility is the job.
  6. 06 / TYPE

    Typography should reduce cognitive load before it adds personality.

    Why it works
    Plain language and disciplined scale make dense technical material easier to trust.
    Unwind reinterpretation
    Keep organism language vivid, but attach every term to definitions, state, route, and proof.
    Implementation opportunity
    Use text-first proof and bilingual parity before image, canvas, or social-packet text.
  7. 07 / NAV

    Navigation should be recovery, not ornament.

    Why it works
    A serious AI site needs stable escape hatches into product, trust, learning, and action.
    Unwind reinterpretation
    The glass nav, mobile drawer, and footer index keep visitors from getting lost inside the organism.
    Implementation opportunity
    Keep Home, Organisms, Proof, Transmissions, and Build With Us reachable on every compact route.
    Proof route
    Glass Lab Nav
  8. 08 / ATTENTION

    Attention management turns a long page into a guided organism run.

    Why it works
    The visitor always knows which concept they are evaluating and what should come next.
    Unwind reinterpretation
    Choreography, state ladders, and resource routes hold attention without tracking identity.
    Implementation opportunity
    Expose the next proof beat before adding more immersive depth or interactive motion.
  9. 09 / EMOTION

    Emotional progression should move from curiosity to bounded agency.

    Why it works
    A visitor can feel possibility without being pushed into blind trust.
    Unwind reinterpretation
    Infinity Mirror, Trust Progression, and Conversation Gateway turn feeling into proof, route, and consent.
    Implementation opportunity
    Keep emotional states reversible and visible, with no profiling, diagnosis, or hidden memory.
  10. 10 / PERF

    Performance strategy is trust strategy.

    Why it works
    A credible technical site loads meaning before optional runtime depth.
    Unwind reinterpretation
    Semantic HTML, SVG, CSS, and bounded JavaScript carry the story before future WebGL or framework migration.
    Implementation opportunity
    Keep performance budgets visible beside runtime ambition, and shut down depth on mobile or reduced motion.
Runtime budget ledger

The organism stays alive because depth has a cost ceiling.

Performance is part of proof. Every runtime lane names what it may load, what it must prove, and when it shuts down before visual ambition becomes drag.

Open budget packet Open build evidence Open asset manifest
  1. 01 / HTML

    Meaning ships before effects.

    Budget
    Critical content ships as semantic HTML first.
    Allowed
    Route copy, proof links, schema, i18n text, and state labels.
    Stop
    No canvas, SVG, or WebGL surface may carry the only meaning.
  2. 02 / CSS SVG

    Motion stays lightweight and reversible.

    Budget
    Textless SVGs target under 20 KB when possible.
    Allowed
    Opacity and transform CSS, visible focus, and reduced-motion static fallbacks.
    Stop
    No scroll hijack, no motion-only proof, and no animated layout dimensions.
  3. 03 / JS

    Shared runtime stays narrow.

    Budget
    The current Vite runtime remains dependency-free for single visual enhancements.
    Allowed
    Language switching, drawer navigation, semantic selectors, and bounded chat routing.
    Stop
    No library is added for one visual surface; no hidden polling, personalization, or status promotion.
  4. 04 / MEDIA

    Distribution assets stay explicit.

    Budget
    PNG previews load lazily and ZIP downloads require explicit action.
    Allowed
    Reviewed carousel previews, caption packets, and download packets.
    Stop
    No autoplay video dependency and no automatic public posting authority.
  5. 05 / 3D

    Three.js remains a gated future lane.

    Budget
    WebGL is excluded from production routes until a route-specific approval gate exists.
    Allowed
    Optional isolated leaf after semantic fallback, cleanup, and mobile shutdown are proven.
    Stop
    No first-viewport blocking, no mobile default, and no deployment without approval.
  6. 06 / API

    Intake stays bounded before authority.

    Budget
    Same-origin subscriber intake remains the only live write path on the public site.
    Allowed
    Subscribe API and Conversation Gateway routing with proof links and human approval boundaries.
    Stop
    No private data pull, spend, outreach, public posting, deployment, or Web3 broadcast.
Access and mobile ledger

The organism must stay usable when the surface gets small, still, or silent.

Accessibility and mobile strategy are proof requirements, not cleanup tasks. Every compact or reduced surface must preserve route recovery, readable meaning, visible focus, and authority boundaries before richer motion or depth appears.

Open access packet Home recovery route
  1. 01 / KEYS

    Routes must remain reachable without a pointer.

    Rule
    Native links, buttons, labels, Escape close, and visible focus come before custom gestures.
    Compact behavior
    The tab order follows the reading order and hash links land below the fixed glass nav.
    Stop
    No pointer-only map, keyboard trap, invisible focus, or unreachable home route ships.
  2. 02 / DRAWER

    Compact navigation becomes recovery, not compression.

    Rule
    When route labels collide, the right-side glass drawer wins over squeezed desktop nav.
    Compact behavior
    Home, organisms, proof, transmissions, and Build With Us remain one gesture away.
    Stop
    No lost-in-index state, brand collision, horizontal overflow, or hidden CTA.
  3. 03 / STILL

    Reduced motion keeps the same story.

    Rule
    Motion can clarify signal, memory, proof, or boundary, but it cannot carry the only meaning.
    Compact behavior
    Static order, semantic labels, and proof links remain readable when motion is off.
    Stop
    No scroll hijack, motion-only proof, or canvas dependency for comprehension.
  4. 04 / ES EN

    Language parity carries the same authority boundary.

    Rule
    English and Spanish must preserve state labels, proof routes, and stop conditions.
    Compact behavior
    Long translated labels can wrap without hiding route meaning or buttons.
    Stop
    No English-only authority claim, route label, or form boundary ships.
  5. 05 / TEXT

    Visuals can support proof, but text must hold it.

    Rule
    Critical meaning lives in HTML, i18n, schema, metadata, specs, and tests before assets.
    Compact behavior
    Diagrams collapse into cards, ledgers, or lists with proof links still visible.
    Stop
    No image, SVG, canvas, or social slide becomes the only source of truth.
  6. 06 / INPUT

    Intake remains labeled, bounded, and recoverable.

    Rule
    Forms and chat prompts expose purpose, labels, helper text, error states, and authority limits.
    Compact behavior
    The Brain gateway and subscriber form remain readable without hiding privacy or proof links.
    Stop
    No hidden data pull, silent execution, deployment, public post, spend, or Web3 broadcast follows input.
System reflection ledger

Every public surface must point back to a real organism layer.

The frontend is allowed to feel alive only when it shows what it represents: gateway, cortex, memory, cells, proof return, simulation, or approval. This ledger keeps visual intelligence tied to inspectable system truth.

Open reflection packet Study organism stack
  1. 01 / SIGNAL

    The hero pulse represents routed intent, not atmosphere.

    System
    Visitor signal moving through gateway, cortex, memory, proof, and approval boundary.
    State
    Prototype interface over static public proof.
    Stop
    No canvas, glow, or animation may carry the only meaning or imply live autonomy.
  2. 02 / GATEWAY

    The Brain gateway routes first context before it promises action.

    System
    Starter prompts, bounded chat routing, subscriber intake, and proof-first next paths.
    State
    Prototype conversation surface with live subscriber intake.
    Stop
    No hidden file write, deployment, private data pull, public post, spend, outreach, or Web3 broadcast follows input.
  3. 03 / MEMORY

    Transmissions turn release motion into public memory.

    System
    Build records, approval notes, release packets, captions, and social carousel handoff assets.
    State
    Live for published records; manual for posting.
    Stop
    No transmission, caption, carousel, or public post moves without review and human approval.
  4. 04 / MIRROR

    Infinity Mirror reflects human signal without judging identity.

    System
    Reflection session, desire translation, proof return, and visible authority gradient.
    State
    Prototype.
    Stop
    No diagnosis, identity inference, hidden memory, forced camera, or public action.
  5. 05 / WEB3

    Financial organisms show simulation before money motion.

    System
    Read-only Web3 research, trust-layer maps, simulation console, and unsigned review packets.
    State
    Research.
    Stop
    No private keys, hidden wallet path, transaction signing, spend, or broadcast by default.
  6. 06 / CELLS

    Brain Cell Architecture shows growth behind sandbox and approval.

    System
    Cell lifecycle, sandbox checks, approval gates, source control, and proof before integration.
    State
    Experimental.
    Stop
    No generated cell integrates itself without tests, sandbox evidence, source review, and human approval.
Rollout readiness ledger

Public motion waits until the organism can prove what changed.

The production rollout plan is a trust surface. Each phase must name exit evidence, release gate, rollback path, and authority boundary before local proof becomes a public alias.

Open rollout packet Release memory
  1. 01 / CLARITY

    Navigation and state labels prove the first path.

    Exit evidence
    Glass nav, home recovery, state ladder, and mobile drawer are verified locally.
    Release gate
    No production push until the user explicitly asks to deploy this version.
    Boundary
    Navigation cannot infer intent, personalize, or execute a workflow.
  2. 02 / PROOF

    Claims move only when proof sits beside them.

    Exit evidence
    Capability ledgers, source translation, runtime budget, access ledger, metadata, and tests name each surface.
    Release gate
    Every new claim needs a route, state label, proof source, and stop condition.
    Boundary
    Proof proximity cannot promote research, prototypes, or local proof into live autonomy.
  3. 03 / RUNTIME

    Runtime depth earns its place through cost and meaning.

    Exit evidence
    Maps, consoles, motion contracts, and budget lanes represent real workflows before animation expands.
    Release gate
    No dependency, WebGL, polling, or richer media without fallback, mobile behavior, cleanup, and approval.
    Boundary
    Motion explains intelligence; it never becomes the only proof.
  4. 04 / MIGRATION

    React and Next remain an option, not a hidden rewrite.

    Exit evidence
    Static surfaces, public specs, server-rendered defaults, and isolated client leaves are mapped before migration.
    Release gate
    No framework migration starts without explicit approval, parity tests, and preserved public routes.
    Boundary
    Migration contracts cannot deploy, install authority, or rewrite the organism identity.
  5. 05 / LIVE

    Living proof connects only to verified sources.

    Exit evidence
    Live status connects to verified backend sources, transmissions, approval records, and social packets.
    Release gate
    Manual, stale, research, prototype, and live states remain separate at the moment of release.
    Boundary
    No alias, transmission, status, public post, outreach, spend, or Web3 broadcast moves without human approval.
Production checkpoint / Local proof

The public alias now has a reviewable deployment trail.

The latest approved deploy is recorded as evidence instead of invisible ceremony: local tests, production build, runtime budget check, Vercel alias, live surface checks, and the manual approval boundary.

Open checkpoint artifact Runtime budget evidence
  1. 01 / VERIFY

    Local proof passed before the alias moved.

    Evidence
    142 Node tests, production Vercel build, runtime budget check, and live homepage metadata checks passed before deploy.
    State
    Local proof recorded for the June 21, 2026 deploy.
    Boundary
    Passing tests does not grant future deploy, posting, spend, outreach, private data, or Web3 authority.
  2. 02 / ALIAS

    The public URL was verified after deployment.

    Evidence
    Vercel reported the approved production checkpoint Ready and aliased the release to www.unwindcode.ai.
    State
    Live public alias.
    Boundary
    The checkpoint observes an approved deploy; it cannot promote future aliases or roll back automatically.
  3. 03 / BUDGET

    Runtime weight is measured, not hand-waved.

    Evidence
    The generated runtime budget artifact reports local_proof_passed and zero violations.
    State
    Local proof backing the deployed build output.
    Boundary
    Budget evidence reports build output only; it cannot install dependencies, monitor users, or approve richer runtime depth.
  4. 04 / HUMAN

    Deployment remains a human-approved action.

    Evidence
    The deploy happened only after the user explicitly requested this page version go live.
    State
    Manual approval boundary.
    Boundary
    No future deployment, transmission, public post, spend, outreach, or Web3 broadcast moves without a new explicit approval.
Live parity gate / Local proof

Verified local proof waits for explicit production approval.

This gate keeps the organism honest when local proof has moved ahead of the public alias. It separates current local evidence, current live evidence, deploy approval, and rollback proof before anyone calls the goal complete.

Open implementation packet Open checkpoint
  1. 01 / LOCAL

    Local proof can be ready before production changes.

    Evidence
    Build, runtime budget, route metadata, source snapshot, i18n shards, and tests pass in the current worktree.
    State
    Local proof.
    Boundary
    Local proof does not deploy, promote an alias, post publicly, spend, pull private data, or broadcast Web3.
  2. 02 / LIVE

    Production needs its own cache-busted check.

    Evidence
    The public alias must be checked after deployment for homepage, proof ledger, checkpoint artifact, discovery files, and API boundaries.
    State
    Live only after explicit deploy and inspection.
    Boundary
    A local pass cannot be described as live parity until the public alias serves the same proof.
  3. 03 / APPROVE

    The human approval boundary is part of the architecture.

    Evidence
    A production push can happen only when the user explicitly asks to deploy this exact version.
    State
    Manual approval required.
    Boundary
    The gate cannot approve deployment, rollback, monitoring, outreach, spending, files, public posting, or Web3 motion.
  4. 04 / CLAIM

    Goal completion waits for live evidence when the goal is public.

    Evidence
    Completion needs source freshness, local proof, public route parity, discovery parity, and authority boundaries to agree.
    State
    Not complete while public parity is unverified.
    Boundary
    No completion claim may shrink the objective to local evidence if the public site is still behind.
Experience evolution acceptance

The goal stays visible until every evolution claim has evidence.

This ledger maps the Anthropic-to-Unwind evolution goal into inspectable proof: source freshness, identity preservation, backend reflection, experience research, implementation architecture, and rollout authority.

Open audit Open packet
  1. 01 / SOURCE

    Outside inspiration remains dated and non-clone.

    Requirement
    Analyze Anthropic for principles without copying its design, motion, section rhythm, or authority language.
    State
    Live source provenance.
    Stop
    Re-check the source before future source-inspired work; stale memory cannot ship as current evidence.
  2. 02 / CENTER

    The organism center is preserved instead of replaced.

    Requirement
    Strengthen Organisms, Infinity Mirror, Brain Cell Architecture, Visual Cortex, Research, Financial Organisms, and philosophy.
    State
    Live identity routes plus local-proof metaphor contracts.
    Stop
    No redesign may flatten the ecosystem into generic apps or hide maturity labels.
  3. 03 / SYSTEM

    Frontend intelligence maps to real backend layers.

    Requirement
    Every dashboard, visual, status, and interaction must represent a workflow, memory layer, research loop, deployment, or organism capability.
    State
    Mixed: Live, Prototype, Research, Experimental.
    Stop
    Decorative complexity, hidden telemetry, runtime authority, and unlabeled future capability stay blocked.
  4. 04 / RESEARCH

    Experience research becomes a build map.

    Requirement
    Cover IA, storytelling, scroll choreography, motion, hierarchy, typography, navigation, attention, emotion, access, mobile, SEO, and performance.
    State
    Local proof and public audit.
    Stop
    Recommendations without proof routes, boundaries, mobile behavior, or reduced-motion meaning do not move forward.
  5. 05 / BUILD

    Future implementation stays ready, gated, and reversible.

    Requirement
    Produce React/Next structure, Framer specs, Three.js opportunities, design tokens, asset requirements, and performance budgets.
    State
    Local proof; no migration approval.
    Stop
    No dependency, migration, WebGL, Framer, GSAP, or Three runtime ships without fallback, cleanup, budget, and explicit approval.
  6. 06 / RELEASE

    Production motion remains human-approved and inspectable.

    Requirement
    Preserve rollout plan, SEO/discovery files, tests, runtime budgets, checkpoint evidence, and manual deploy boundary.
    State
    Live alias verified; next deploy not approved.
    Stop
    No future deployment, post, outreach, spend, private data pull, filesystem write, rollback, or Web3 broadcast moves without explicit approval.
Completion audit / Asset governance

The organism can show progress without pretending the goal is finished.

This audit separates proven surfaces, blueprint-only architecture, governed asset pipelines, live release proof, and blocked authority before anyone treats the active frontend evolution goal as complete.

Open completion audit Asset governance
  1. 01 / PROVEN

    Current public proof can be trusted only where evidence is named.

    State
    Proven current for source, organism identity, conversion paths, and public proof routes.
    Audit
    Evidence must stay current at claim time; stale source memory or route drift fails the audit.
    Blocked
    No copied design, hidden authority, unlabeled capability, or completion-by-vibe.
  2. 02 / ASSETS

    Premium visuals must earn their pixels through system meaning.

    State
    Governed pipeline for hero visuals, organism maps, diagrams, social previews, motion layers, pseudo-3D, canvas, and WebGL candidates.
    Audit
    Every asset needs purpose, text policy, motion policy, mobile behavior, dependencies, target weight, and proof route.
    Blocked
    No decorative media, unoptimized image weight, text trapped in images, or mobile-heavy WebGL.
  3. 03 / BLUEPRINT

    Future React, Next, Framer, and Three.js work stays gated.

    State
    Implementation-ready contracts exist; runtime migration and new dependencies are not approved.
    Audit
    Any immersive effect needs fallback, reduced-motion behavior, cleanup, budget proof, and route-specific value.
    Blocked
    No framework rewrite, Framer/GSAP runtime, Three.js scene, particle system, or shader layer without explicit approval.
  4. 04 / CLAIM

    The completion claim remains locked until current evidence proves every lane.

    State
    Completion not claimed by this audit.
    Audit
    Tests, build, budget, public alias, discovery files, route parity, and authority boundaries must agree at claim time.
    Blocked
    No deploy, public post, outreach, spend, private data pull, file write, status change, or Web3 broadcast without a new explicit approval.
Requirement coverage ledger / Local proof

Every named evolution requirement must point to visible evidence.

This ledger expands the goal into audit, research, IA, component, motion, metaphor, implementation, access, SEO, and rollout lanes so the objective cannot quietly shrink to whichever surface was edited last.

Open audit Open implementation packet
  1. 01 / SOURCE

    Source research stays current, principled, and non-clone.

    Covers
    Anthropic analysis, design research, storytelling flow, attention management, information architecture, and emotional progression.
    State
    Live source provenance plus local-proof research translation.
    Stop
    No copied section rhythm, stale source memory, implied affiliation, or borrowed authority language may ship.
  2. 02 / MAP

    Audit findings become route jobs and component contracts.

    Covers
    UX audit, information architecture improvements, component recommendations, visual hierarchy, typography, navigation, and conversion paths.
    State
    Local proof; route and component contracts exist before framework migration.
    Stop
    Recommendations without a route, proof artifact, state label, mobile behavior, and authority boundary remain rejected.
  3. 03 / MOTION

    Motion explains intelligence instead of decorating it.

    Covers
    Motion systems for intelligence, learning, memory, reflection, evolution, emergence, scroll choreography, Framer specs, and Three.js gates.
    State
    Live semantic motion contracts plus local-proof future runtime gates.
    Stop
    No motion-only proof, scroll hijack, unlabeled WebGL, dependency install, or animation without reduced-motion meaning.
  4. 04 / BIOLOGY

    Digital biology strengthens the existing organism center.

    Covers
    Infinity, reflection, recursion, neural growth, cognitive evolution, living systems, intelligence organisms, and digital biology.
    State
    Mixed live routes and local-proof metaphor contracts.
    Stop
    No single visual metaphor may replace Organisms, Infinity Mirror, Brain Cell Architecture, Visual Cortex, Research, Financial Organisms, or philosophy.
  5. 05 / STACK

    Implementation architecture is ready but not secretly approved.

    Covers
    React architecture, Next.js structure, Framer Motion specs, Three.js opportunities, design tokens, asset requirements, and performance budgets.
    State
    Local proof; no React/Next migration or runtime dependency approval.
    Stop
    No framework migration, Framer leaf, GSAP sequence, Three/WebGL route, token drift, or asset expansion without fallback, cleanup, budget, and approval.
  6. 06 / RELEASE

    Access, SEO, rollout, and production proof stay tied together.

    Covers
    Accessibility improvements, mobile strategy, SEO preservation, production rollout plan, performance strategy, tests, and deployment checkpoints.
    State
    Live discovery layer with local-proof rollout and budget gates.
    Stop
    No deployment, public posting, outreach, spending, private data, files, rollback, or Web3 broadcast without a new explicit approval.
Objective deliverable index / Local proof

Every named deliverable has a proof route and a stop condition.

The objective names concrete outputs. This index keeps each one visible so the work cannot hide behind a broad audit, a good-looking page, or a passing test run.

Open research matrix Open build blueprint
  1. UX Audit

    User experience risk is inspected before new surfaces ship.

    State
    Local proof with public proof route.
    Stop
    No UX claim ships without a visitor question, proof route, mobile behavior, and authority boundary.
  2. Design Research

    External inspiration becomes source-bound translation.

    State
    Live provenance plus local-proof interpretation.
    Stop
    No copied design rhythm, endorsement, affiliation, stale source memory, or borrowed authority.
  3. Information Architecture Improvements

    Route jobs define what each page must prove.

    State
    Local proof in the machine-readable packet.
    Stop
    No route expansion without required surfaces, state policy, discovery files, and tests.
  4. Component Recommendations

    Recommended components inherit fields, states, and authority boundaries.

    State
    Local proof before future framework migration.
    Stop
    No component becomes production work without rendering mode, fields, interaction, and authority boundary.
  5. Motion Architecture

    Motion is allowed only when it explains a system.

    State
    Live semantic motion rules plus local-proof future specs.
    Stop
    No scroll hijack, motion-only meaning, unbounded loop, or dependency-led animation.
  6. Accessibility Improvements

    Access is a release gate, not polish.

    State
    Local proof with tested language and motion preferences.
    Stop
    No interaction ships without keyboard route, focus state, reduced-motion behavior, and text-first proof.
  7. Mobile Strategy

    Compact screens keep the organism navigable.

    State
    Live navigation rule with local browser checks.
    Stop
    No hidden text, horizontal overflow, gesture-only controls, or blocked route back home.
  8. SEO Preservation

    Discovery files must repeat the same truth humans see.

    State
    Live crawl and AI-readable contract layer.
    Stop
    No schema, sitemap, llms, preview, or service claim may outrun visible proof.
  9. Production Rollout Plan

    Local proof waits for explicit release authority.

    State
    Live release rule with local-proof gates.
    Stop
    No deploy, alias promotion, rollback, public posting, spend, outreach, or Web3 motion without approval.
  10. React Architecture

    Future React work defaults to server-rendered organism contracts.

    State
    Local proof; framework migration is not approved.
    Stop
    No client leaf or state store without isolated job, fallback, cleanup, and budget proof.
  11. Next.js Structure

    Future route groups preserve the current public contract.

    State
    Local proof; no App Router migration yet.
    Stop
    No route migration without redirects, metadata parity, i18n parity, API boundary tests, and rollback.
  12. Framer Motion Specs

    Framer is reserved for isolated meaning-bearing leaves.

    State
    Local proof; dependency not installed or approved.
    Stop
    No continuous animation without reduced motion, memoized leaf, static fallback, and one system meaning.
  13. Three.js Opportunities

    Three.js remains optional until depth proves its job.

    State
    Local proof; no WebGL route approval.
    Stop
    No WebGL without semantic fallback, reduced motion, mobile budget, kill switch, and proof route.
  14. Design Tokens

    Tokens encode digital biology without becoming decoration.

    State
    Local proof with live semantic route.
    Stop
    No one-note palette, illegible glass, color-only state, nested cards, or motion-only meaning.
  15. Asset Requirements

    Every asset must prove its job before it earns pixels.

    State
    Live governance with local-proof manifest tests.
    Stop
    No visual asset may carry critical text, fake telemetry, hidden proof, or decorative complexity.
  16. Performance Budgets

    Runtime cost is measured before richer depth expands.

    State
    Local proof passed with release-gated evidence.
    Stop
    No heavy route, media packet, route dictionary, WebGL lane, or dependency ships without budget evidence.
Production recommendation gate / Local proof

A recommendation is not production-ready until its evidence, fallback, and authority boundary are visible.

This gate keeps future architecture advice from becoming vague ambition. Every React, Next.js, Framer, Three.js, token, asset, or rollout recommendation must prove what exists now, what remains only a blueprint, and what is blocked.

Open implementation contract Open runtime budget
  1. 01 / CURRENT

    The current static organism surface remains the source of truth.

    Proof required
    Semantic Vite pages, i18n source, discovery files, tests, build, and runtime budget evidence stay aligned.
    State
    Live public site plus local-proof evolution surface.
    Blocked
    No hidden runtime, telemetry, personalization, status mutation, deploy action, or decorative intelligence may be recommended as production.
  2. 02 / FRAMEWORK

    React and Next.js stay blueprints until parity is proven route by route.

    Proof required
    Server-rendered defaults, isolated client leaves, clean redirects, metadata parity, i18n parity, API boundary tests, and rollback route.
    State
    Blueprint only; no framework migration approval.
    Blocked
    No dependency install, App Router migration, route rewrite, API rewrite, or client-state expansion without explicit approval.
  3. 03 / MOTION

    Framer or GSAP earns a place only when motion explains a system.

    Proof required
    One system meaning, semantic fallback, reduced-motion behavior, transform-or-opacity only, cleanup, memoized leaf, and measurable budget.
    Evidence route
    Motion Meaning Ledger
    State
    CSS-first local proof; runtime motion dependency not approved.
    Blocked
    No scroll hijack, mood-only animation, perpetual CPU loop, motion-only proof, or copied source choreography.
  4. 04 / DEPTH

    Three.js remains optional until depth improves inspection.

    Proof required
    Route-specific depth job, static semantic fallback, pixel checks, mobile shutdown path, reduced-motion exit, kill switch, and budget evidence.
    State
    Opportunity only; no WebGL route approval.
    Blocked
    No WebGL as mobile core meaning, no canvas-only proof, no heavy asset path, and no hidden tracking renderer.
  5. 05 / MATERIAL

    Tokens and assets must prove a system job before they earn pixels.

    Proof required
    Design-token meaning, asset purpose, text policy, mobile policy, dependency list, target size, and proof route.
    State
    Live governance with local-proof manifest coverage.
    Blocked
    No one-note palette, illegible glass, nested cards, text trapped in images, fake telemetry, or decorative asset bloat.
  6. 06 / RELEASE

    Release recommendations remain manual until a fresh approval moves them.

    Proof required
    Tests, build, budget, diff check, explicit deploy request, Vercel inspect, alias verification, route smoke, API smoke, and log check when available.
    Evidence route
    Live Parity Gate
    State
    Manual release gate; no standing deploy authority.
    Blocked
    No future deploy, alias promotion, rollback, social post, outreach, spend, private data pull, filesystem write, or Web3 broadcast.
Discovery preservation ledger

The organism must stay findable without becoming overclaimed.

SEO is treated as public proof infrastructure: canonical routes, schema, AI-readable contracts, social previews, source provenance, and runtime budgets must agree before a surface is trusted.

Open sitemap Open llms.txt
  1. 01 / ROUTES

    Canonical paths stay durable before the story expands.

    Surface
    Homepage, organism routes, proof, transmissions, philosophy, vision, and build gateway.
    State
    Live crawl contract.
    Stop
    No public route changes without sitemap, canonical metadata, internal links, tests, and redirects when needed.
  2. 02 / SCHEMA

    Structured data cannot outrun visible proof.

    Surface
    Organization, WebSite, FAQ, ImageObject, CollectionPage, DefinedTerm, TechArticle, and Service schema.
    State
    Live metadata with local proof tests.
    Stop
    No schema may imply live autonomy, financial outcome, diagnosis, affiliation, or authority not visible on the page.
  3. 03 / MACHINES

    AI-readable files name the same boundaries humans see.

    Surface
    llms.txt, ai-services.json, asset manifest, runtime evidence, and implementation packet.
    State
    Live machine-readable boundary layer.
    Stop
    No hidden telemetry, personalization claim, status promotion, or private capability can appear in machine files without visible proof.
  4. 04 / PREVIEW

    Social previews introduce the lab without replacing inspection.

    Surface
    Open Graph, Twitter metadata, governed preview asset, and social carousel packets.
    State
    Live preview layer plus manual social packets.
    Stop
    No preview asset may carry the only proof, hide maturity labels, or imply public posting authority.
  5. 05 / SOURCE

    External inspiration stays dated, cited, and non-affiliated.

    Surface
    Current source snapshot, non-clone boundary, rejected uses, and Unwind translation rule.
    State
    Live provenance gate.
    Stop
    No stale source memory, copied rhythm, endorsement, affiliation, or source-inspired deploy moves without re-checking.
  6. 06 / BUDGET

    Discovery performance is measured after the story grows.

    Surface
    Shared CSS, shared i18n loader, route dictionaries, dependency-free runtime, route scripts, and media assets.
    State
    Local proof passed.
    Stop
    No language-heavy surface, WebGL lane, media packet, or dependency ships without budget evidence and rollback route.
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