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 layer makes the next operating decision easier: trace the claim, test runtime-dependent behavior, and name the receiving surface before the handoff.

Current state Read
Evidence selected
Decision object

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.

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

Featured Work

Experiments, field notes, and patterns worth inspecting first.

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.