Research / Source-bound organism

Research Organisms turn unknowns into proof paths.

The research lane studies sources, questions, experiments, and evidence gaps without pretending exploration is certainty. Its job is to return a source map, testable claim, and publication boundary before an idea becomes doctrine.

Read research transmissions→ Inspect proof gates
Product path

A serious research lane keeps speculation labeled.

Research Organisms let the lab study AI patterns, cultural intelligence, backend behavior, Web3 signals, and product questions while preserving caveats, sources, and human review.

Open the vision roadmap Read the proof library
Stage
Research lane for source-bound organism learning.
Input
Sources, questions, evidence gaps, experiment notes, public signals, and operator context.
Cells
Source mapping, hypothesis framing, experiment design, synthesis, and publication review.
Boundary
Research can propose a claim; it cannot turn uncertainty into public certainty without review.
Proof
Transmissions, source ledgers, audit packets, and proof gates keep the trail inspectable.
Capability ledger

What Research Organisms can study, what stays uncertain, and where proof lives.

Before research becomes product language, the lane names its boundary: sources, questions, experiments, synthesis, review, and publication gate. The organism may map a claim; it cannot make the claim authoritative by sounding confident.

  1. 01 / Source

    Turn material into a source packet.

    The organism can gather supplied sources, public artifacts, prior transmissions, and observed system behavior into a map a human can inspect.

    Input
    Public sources, supplied files, audit notes, transmissions, and current system evidence.
    Output
    A source packet with provenance, open questions, and exclusions.
    Blocked claim
    No fabricated citation, hidden source, scraped private context, or copied institutional authority.
  2. 02 / Question

    Keep unknowns alive as testable questions.

    Research becomes useful when it preserves uncertainty long enough to design a better experiment, comparison, or proof request.

    Memory boundary
    Only reviewed context and public proof should shape the next research loop.
    Output
    A hypothesis map with assumptions, counterpoints, caveats, and evidence needed.
    Blocked claim
    No certainty theater, hidden consensus, or claim that a pattern proves causation.
  3. 03 / Experiment

    Route the question into a bounded experiment.

    The research lane can design a simulation, local test, data review, interface prototype, or source comparison that makes the claim easier to inspect.

    Tool boundary
    No hidden data pull, private scraping, wallet action, public post, deployment, or filesystem write by default.
    Output
    An experiment packet with method, fixtures, result, uncertainty, and next proof request.
    Blocked claim
    No live-world action or product promise until the experiment is reviewed.
  4. 04 / Publish

    Publish only after review preserves the caveats.

    A research output becomes public only when sources, limitations, state labels, proof links, and human approval travel with it.

    Approval boundary
    Human review approves public wording, state label, source scope, and proof route.
    Output
    A transmission, spec, audit note, or refused claim with a visible trail.
    Blocked claim
    No public certainty, benchmark, market claim, or research authority without evidence and review.
Translation ledger

Research becomes product language only after the proof survives translation.

Each research output passes through source scope, backend reality, experiment evidence, allowed next state, and blocked claim before it can become a transmission, prototype, or build packet.

Inspect source translation Inspect system reflection
  1. 01

    External pattern becomes Unwind principle.

    Research
    Question
    Which storytelling, trust, or IA principle is useful without copying the design skin?
    Allowed next
    Audit note, component contract, or local proof surface.
    Blocked claim
    No affiliation, endorsement, copied layout, copied taxonomy, or borrowed authority.
  2. 02

    Backend behavior becomes visible interface truth.

    Prototype
    Question
    What workflow, memory layer, cell, gateway, approval gate, or public artifact does the visual represent?
    Allowed next
    Semantic interface surface with state label and proof route.
    Blocked claim
    No decorative intelligence, hidden telemetry, private memory, or live autonomy claim.
  3. 03

    Experiment becomes local proof before product promise.

    Local proof
    Question
    Can the claim survive a local test, browser check, metadata sync, or source-backed review?
    Allowed next
    Prototype lane, implementation packet, or refused claim.
    Blocked claim
    No live status, deployment, public post, spend, private data pull, or Web3 broadcast.
  4. 04

    Reviewed output becomes public memory with caveats attached.

    Live record
    Question
    Can a reader inspect what changed, what proves it, what remains manual, and where to go next?
    Allowed next
    Transmission, social packet, build packet, or research note.
    Blocked claim
    No unattended publishing, status promotion, outreach, or authority expansion.
Research field

A source enters as a question and leaves as a reviewed proof path.

The field visual is intentionally textless: the meaning stays in semantic HTML. Source, question, experiment, and publication gate are the actual research loop.

Read the experience audit Map a research packet
  1. 01Source packet

    Name provenance, gaps, exclusions, and what cannot be inferred.

  2. 02Question map

    Turn the unknown into a hypothesis, counterpoint, and evidence request.

  3. 03Bounded experiment

    Run only the local, simulated, or reviewed test the method allows.

  4. 04Publication gate

    Ship the caveat, source, state label, and proof link together or do not ship.