From a question to a decision rule
These are interpretive connections between my AI-assisted research notes and projects. They describe useful parallels, rather than claiming historical influence without a dated decision record.
AI, From the Atoms Up
- Question
- What turns a model into an operational AI system?
- Working model
- A technical stack crosses concerns such as state, identity, evaluation, and human authority.
- Decision rule
- Name the system boundary before assigning a capability or a failure to the model.
- Applied example
- The Fantopy orchestration record separates agent-generated pull requests from human merge authority. Terminus separates reasoning from permission to execute.
Read AI, From the Atoms Up and its sourcesFunctional Anatomy of Systems
- Question
- How do complex systems divide responsibility without losing coherence?
- Working model
- Specialized functions need records, communication, feedback, and boundaries around ownership.
- Decision rule
- When a system fails, identify which responsibility is absent, overloaded, or held by the wrong component.
- Applied example
- Terminus gives specialists ownership of their domain records and lets a shared view reference their evidence.
Read Functional Anatomy of Systems and its sourcesRed Trees
- Question
- How does an inherited error survive, and how should it be corrected?
- Working model
- Claims depend on observations and on other claims. Correction should follow those dependencies.
- Decision rule
- Trace a conclusion to its evidence before trusting or repairing it.
- Applied example
- The Fantopy record describes independent scoring reconciliation. Terminus makes stale source evidence visible and proposes wider correction propagation.
Read Red Trees and its sourcesAll Roads Lead to Rock
- Question
- What changes when one technical layer hides the complexity of another?
- Working model
- Each abstraction transfers control and responsibility; failures can expose the hidden layer again.
- Decision rule
- State who owns the underlying behavior and what must remain observable across the boundary.
- Applied example
- Constant separates conversation continuity from an agent runtime. Fleetwatch observes machines over SSH without installing its own agent on them.
Read All Roads Lead to Rock and its sourcesBusiness Shape Morphology
- Question
- How do capabilities, constraints, and recurring market gaps shape a product?
- Working model
- The visible product depends on supporting functions such as coordination, trust, operations, and recovery.
- Decision rule
- Design around the workflow that owns the constraint, including the work outside the interface.
- Applied example
- Ever keeps the hosts' spreadsheet in the operating workflow and connects it to invitation and RSVP software.
Read Business Shape Morphology and its sourcesFurther parallels
Workbench packages methods with their boundaries. Terminus retains incident lessons and recovery procedures alongside its tools.
The Terminus case study uses an explicitly fictional walkthrough to explain intended behavior, separately from its operating evidence.
Terminus's permission lifecycle is an engineering parallel to that question, with explicit grants and human review.
Research method and limits
I choose the questions and direction; AI assists with research, synthesis, and drafting. The articles link their sources and discuss uncertainty. They are personal research notes, not peer-reviewed scholarship. An analogy is a way to inspect a design, not evidence that the design works.
About the research notebook