A survey craft leaving a directional wake across dark water
CREATE SOMETHING .io

Research for automation you can defend.

CREATE SOMETHING .io turns experiments, papers, and field notes into a usable research layer for operators. The goal is evidence you can carry into the next build, review, or production decision.

  • published experiments + papers 21
  • research categories 1
  • featured artifacts to inspect first 6
  • database / automation / judgment layers 3
Research decision path

Start from evidence. Decide whether to read, test, or scope.

The research decision and its artifacts now share one surface: trace the claim, inspect the relevant work, and name the receiving lane before handoff.

01 / 03 Evidence selected

Start from the artifact trail.

Start from operator friction, runtime behavior, and implementation receipts. Papers, experiments, and field notes stay tied to the workflow and make the claim, artifact, methodology, and next move inspectable.

Read: Featured Work

Experiments, field notes, and patterns that support this decision.

Evidence
  • Paper or experiment names the source workflow and operating question
  • Claim is tied to methodology, implementation notes, or the research graph
  • Operator notes explain why the workflow exists and where it breaks
Receipts
paper archivemethodologyresearch graph
02 / 03 Runtime proof needed

Move the claim into a live surface.

Compare cost, speed, and maintenance drag across AI-native stacks. When the claim still depends on timing, state, or failure behavior, move it into the workbench instead of adding another paragraph.

Validate: Featured Work

Experiments, field notes, and patterns that support this decision.

Evidence
  • Pattern has a concrete execution question
  • Timing, state, and failure behavior are visible
  • Implementation tradeoffs are written for operators, not leaderboard chatter
Receipts
runtime notemotion outputdata trace
03 / 03 Delivery decision

Carry proven evidence into delivery.

Turn proven judgment into policy packs, release checks, contracts, and runbooks. When the risk is commercial, operational, or reputational, route the evidence to a scoped workflow with an explicit owner.

Scope: Featured Work

Experiments, field notes, and patterns that support this decision.

Evidence
  • Database / Automation / Judgment remains the operating frame
  • Evidence points to controls, policy, and recovery
  • Delivery handoff has an owner and a clear first lane
Receipts
handoff notepolicy cuemapping session
Property progression

Move the evidence into its next operating surface.

.io does the reading so the rest of CREATE SOMETHING can move faster. Start with the methodology, inspect the papers and graph, use .space for runtime validation, .learn for guided practice, .ltd for the thesis, and .agency when a named workflow is ready to map.

You are here .io Research
Owner
Research operator
Authority
Evidence before promotion
Proof
Paper + graph + method
State
ready
  1. 01 .ltd Canon Clarify the principles, standards, and judgment that should guide the work.
  2. 02 .io Research Inspect the evidence, field reports, and operating notes behind the claim.
  3. 03 .learn School Follow a guided path and leave with an inspectable working artifact.
  4. 04 .space Workbench Run the tools and rehearse the behavior before the pattern becomes delivery.
  5. 05 .agency Build Map one workflow, qualify the control boundary, and choose the delivery path.