I use architecture as a precision filter for intuition.
Curiosity may discover the relation. A method gives it a form, a boundary, and a test without pretending that the first elegant pattern is already true.
The loop is deliberately finite. It begins by orienting and ends by returning enough state for another person to inspect or resume the work.
01
Orient
Name the decision and closest sources.
02
Bound
Set scope, authority, and no-touch edges.
03
Classify
Separate source, evidence, inference, and proposal.
04
Compose
Build the smallest useful context and artifact.
05
Build
Make the candidate inspectable.
06
Check
Test one named predicate and seek counterevidence.
07
Decide
Keep consequential meaning and release human-held.
08
Return
Record state, limits, and next responsible action.
02 / Instrument shelf
Small tools that clarify before they scale.
01
Source ledger
What was consulted, in what role, with what omission or freshness limit.
02
Claim card
What is being said, which evidence supports it, and what it does not establish.
03
Check receipt
What was tested, on which input, with which outcome, and what remains unproven.
04
Return record
Current state, owner, uncertainty, and one reliable way back in.
03 / Prompt Engineering Catalog
128 techniques, organized by transformation.
Projected from a 512-record atlas across 64 categories. Each card opens into an 8-section breakdown; the Prompt Lab generates a form-driven template you can copy into any agent.
128 / 128 techniques
04 / Fictional teaching case
A small system boundary under review.
Should a document-indexing concern become its own module? Bind its imports and failures, define the no-touch storage boundary, draft a port, check isolation, and return the decision for human review. This illustrates a method; it is not a client result or released system.