Skip to the studio index
Hearth & Code

Hearthside Meta-Architect / public research studio

Field Journal

H+C / Research StudioPublic orientation · 2026

I build systems that can explain themselves—and leave a way back.

Hearth & Code is my public workbench for research, software, knowledge architecture, prompt practice, and creative systems. I use the Hearthside Meta-Architect as a working name for the craft: forge enough structure to make complexity inspectable, then keep it warm enough to inhabit, question, and revise.

Explore the studio View selected work

Public by the count

  1. 35Method field cards
  2. 128Prompt techniques
  3. 32Fieldcraft field notes
  4. 10Field Journal entries
  5. 8Hearthside essays
  6. 16Dossier entries

01 / Working Archetype

Forge enough structure.
Keep the hearth lit.

I use Hearthside Meta-Architect as a working name for the practice behind this studio. It sits between systems architecture, knowledge engineering, research cartography, specification, toolmaking, and keeping a workshop fit for human use.

The name is a semantic handle—not a credential, diagnosis, or claim that every method here works for everyone.

Read the full working dossier →
  1. 01

    Build the return before the goal

    Leave enough state, source, and next-action context that interruption is survivable.

  2. 02

    Name what kind of thing this is

    Keep source, observation, inference, hypothesis, proposal, and decision from borrowing one another’s authority.

  3. 03

    Keep one protected build lane

    Give exploration room without allowing it to consume every route to completion.

  4. 04

    Require a concrete seam

    Let a new architecture earn attention by improving one handoff, transition, retrieval task, or test.

  5. 05

    Give ideas a waiting room

    Preserve a branch without automatically promoting it into a commitment.

  6. 06

    Use agents as roles, not mystique

    Delegate bounded work while keeping consequential interpretation and release human-held.

  7. 07

    Let creative work test the system

    A structure should support curiosity, meaning, and play as well as control and precision.

  8. 08

    Finish in public-sized pieces

    Prefer a small honest artifact with visible limits to an invisible total system.

02 / Research Studio Index

Six ways into my work.

I give each room its own publication form and evidence boundary. Begin with the kind of material you want to read, use, or inspect.

01Practice library

Methods

I keep thirty-five field cards for orientation, context, evaluation, and responsible return — the 4-lens method family, distinct from the 128-technique prompt catalog.

Open my methods lab
02Public record

Research Library

I gather fifty published works — Field Journal entries, Hearthside essays, Fieldcraft field notes, and method cards — into one searchable workbench.

Enter my research library
03Technique atlas

Prompt engineering

I project 128 prompt techniques from a 512-record atlas. Each opens into an 8-section field file with a form-driven Prompt Lab template generator.

Browse my prompt catalog
04Research programs

Technical reports

I connect TCCP, EKRP, Exocore, and system design through bounded dossiers and public-safe report orientations.

Read my program dossiers
05Evidence desk

Artifacts

I use claim cards, evidence records, diagrams, templates, and correction routes to make the work inspectable.

Inspect my artifact trail
06Selected practice

Portfolio

I collect selected research programs, software systems, publications, and current directions without hiding their posture.

View my selected work

03 / Field Archive

A broad index of the work already on the table.

The counts describe distinct reading families and sometimes overlap: prompt techniques belong to the method fieldbook, and technical articles belong to Published Works. The index is a route map, not an inflated total.

  1. IDX-0135Public learning modules

    Method field cards

    Semantic orientation, Operational Intelligence, prompt and context practice, evaluation, and return. The 4-lens field family distinct from the 128-technique catalog.

    Representative entriesLiteral before normalized · bounded review questions · Power-of-Two bounded structure

    Open the method fieldbook
  2. IDX-02128Public-safe projection

    Prompt engineering techniques

    Projected from a 512-record atlas across 64 categories. Each card opens into an 8-section field file and a form-driven Prompt Lab template generator.

    Representative entriesDynamic Context Assembly · Self-Refine · Goal-Prompt Lifecycle · Receipt-Bound Validation

    Open the Prompt Lab
  3. IDX-0332Source-bound public surface

    Fieldcraft field notes

    Runnable techniques with working examples, counterexamples, and source references. Each note is testable rather than merely described — 111 fixture checks, 31 executable Node commands.

    Representative entriesAcceptance Condition · Bind Every Claim to Evidence · Encode Review State with Rust Typestate

    Open Fieldcraft
  4. IDX-0450Published and authored records

    Published works

    Ten Field Journal entries, eight Hearthside essays, and thirty-two Fieldcraft field notes — every item source-bound with claim labels and a return surface.

    Representative entriesThe Hearthside Meta-Architect · Typed Context for Real Work · Prompting as Interface Design · 32 FC notes

    Enter the reading room
  5. IDX-0506Mixed-maturity public orientation

    Technical report orientations

    TCCP, EKRP, Exocore, the technique atlas, product portfolio, and Core32 evaluation research — each a bounded dossier with its own publication posture.

    Representative entriesProgram dossier · architecture dossier · evaluation research

    Open the report shelf
  6. IDX-0610Public publication

    Field Journal entries

    Long-form work with publication date, source context, and explicit claim labels. Technical articles and shorter essays live beside them in the reading room.

    Representative entriesESS: the thread between thought and action · Designing a genre as a system · A public journal begins with a boundary

    Read the journal
  7. IDX-0708Authored record

    Hearthside essays

    Source-aware essays on meaning, provenance, workbench design, and prompt craft — the longer reasoning behind the technique cards.

    Representative entriesMeaning Before Machinery · A Humane Theory of Provenance · Prompting as Interface Design

    Open the essay shelf
  8. IDX-0816Personal candidate · review requested

    Archetype dossier entries

    Orientation, practice, relations, and continuity for the Hearthside Meta-Architect working profile — D-01 through D-16.

    Representative entriesMinimum viable institutions · constitutional autonomy · integrated archetype

    Open the dossier

04 / Method Architecture

I use methods as routes through uncertainty.

I keep this library practical rather than doctrinal: take a field card, adapt it to your sources and constraints, and preserve what the attempt cannot prove.

  1. 01

    Semantic orientation

    Keep literal evidence, interpreted meaning, and normalized language distinguishable.

  2. 02

    Operational intelligence

    Compare forms, transitions, ownership, and loss without centralizing authority.

  3. 03

    Prompt & context practice

    Design prompts as inspectable task contracts with bounded inputs and effects.

  4. 04

    Evaluation & return

    Check one named predicate, calibrate the claim, and leave a reliable way back.

Open 35 field cards and 128 prompt techniques →

05 / Publication Desk

Recent from my Field Journal.

I use long-form entries to preserve publication date, source context, and claim labels. Technical articles and shorter essays live beside them in the reading room.

  1. 01

    · Field Journal

    ESS: The Thread Between Thought and Action

    A Hearthside orientation to ESS: a candidate framework for carrying provenance, meaning, and human authority across AI-mediated work.

    Read
  2. 02

    · Field Journal

    A Hub That Can Explain Itself

    An eight-stage practical journey for building a small provenance-aware layer around AI-assisted knowledge work.

    Read
  3. 03

    · Field Journal

    The Hearthside Meta-Architect

    A personal reflection on building a humane, governed workbench for nonlinear systems work.

    Read
Browse the journalOpen the Research Library

06 / Selected Portfolio

I make research useful through its artifacts.

This is my selected view across research programs, knowledge systems, software, and public writing. I keep each item’s current posture visible.

Open the full portfolio
  1. TCCP
    Research program

    Typed Context & Control Protocol

    Representations, context, interaction, and proof obligations.

  2. EKRP
    Applied research

    Knowledge Representation Profile

    Human-readable knowledge architecture with explicit provenance.

  3. EXO
    Software system

    Exocore

    A local-first workbench for agents, knowledge, governance, and return.

  4. H+C
    Published practice

    Field Journal

    Essays and technical writing from the workbench of the studio.

07 / Publication Posture

I want the work legible and the claims honest.

Source-aware
Published material names the sources and limits that shape its reading.
Human-released
Automation may prepare and check; publication remains a deliberate human act.
Privacy-preserving
The public studio collects no visitor profile and exposes no private working context.
Corrigible
Evidence, uncertainty, revision, and a route for correction remain visible.

08 / Continue the inquiry

Follow one of my questions.
Bring back a better one.

Browse open questions Begin a correspondence