Skip to content
Hearth & Code

Dossier / Hearthside Meta-Architect

Field Journal

H+C / 08Dossier

I call this working archetype the Hearthside Meta-Architect.

This self-authored field character sheet describes how I try to join forge and hearth in my work. It is a creative working archetype, not a diagnosis or credential.

Open the case file

From my workbench

Personal candidate · review before publication
Hearthside Meta-Architect is a working name, not a credential.

It helps me coordinate forge and hearth: structural rigor with welcome, imaginative reach with concrete seams, and autonomy with visible boundaries.

Read the working archetype →

Hearth & Code / case file HMA-16

Hearthside Meta-Architect

My public working archetype for the practice behind this studio: a creative orientation, not a diagnosis, credential, or autonomous persona.

Role

Creative systems stewardForge + hearth / field research + working craft
Central question
What is the smallest structure that preserves what matters?
Core loop
Orient · bound · compose · check · decide · return
Instruments
Ledger · atlas · protocol · notebook · correction path
Party role
I turn complexity into a shared, reviewable working surface.

How to use this file

Read it as a field guide to working posture.

Each entry has a tendency to notice and a practical move to test. Follow a chapter for a particular kind of question, or use the case-file codes to move directly to a card. The sheet names habits of practice; it does not diagnose a person or confer professional authority.

Chapter I / D-01–D-04

Orientation

How the Hearthside Meta-Architect meets a question.

  1. D-01

    Builder of structures behind structures

    I look beneath visible artifacts for the protocols, permissions, and contexts that shaped them.

    At the tableAsk what conditions made this object possible.
  2. D-02

    Hearthside orientation

    I try to make complicated machinery inhabitable through names, routes, and human-scale surfaces.

    At the tableMake the difficult thing findable.
  3. D-03

    Divergence and convergence

    I let a field widen before reducing it to the smallest structure that can carry a decision.

    At the tableExplore without losing the decision.
  4. D-04

    Meaning needs an interface

    I treat representation as an engineering concern and a human concern at once.

    At the tableGive the idea a form that can be challenged.
Return to case-file index ↑

Chapter II / D-05–D-08

Practice

The working moves, instruments, and pressure checks.

  1. D-05

    Uncertainty as structured state

    I keep unknowns and contradictions present rather than smoothing them into confidence.

    At the tableName what remains unresolved.
  2. D-06

    Intuition with a precision filter

    I let intuition propose, then ask sources, checks, and review to qualify the proposal.

    At the tableSeparate discovery from decision.
  3. D-07

    Relational systems sight

    I notice interfaces, dependencies, and feedback before treating a part as isolated.

    At the tableDraw the relation, not just the inventory.
  4. D-08

    Minimum viable institutions

    I build enough governance to preserve meaning without building a theatre of process.

    At the tableFit the structure to the pressure.
Return to case-file index ↑

Chapter III / D-09–D-12

Relations

How collaboration, metaphor, and permission remain legible.

  1. D-09

    Plural minds, singular accountability

    I use collaboration and tools while keeping consequential judgment human-held.

    At the tableKeep responsibility legible.
  2. D-10

    Archetypes as semantic handles

    I use memorable roles to compress recurring practices without making them authority.

    At the tableName a pattern without mythologizing it.
  3. D-11

    World-building as systems prototyping

    I use imaginative worlds to test coherence, experience, and relation.

    At the tableLet a world reveal a system.
  4. D-12

    Constitutional autonomy

    I prefer bounded permission, explicit release, and visible stop conditions.

    At the tableFreedom inside a legible envelope.
Return to case-file index ↑

Chapter IV / D-13–D-16

Continuity

How the work remains revisable, finite, and hospitable to a future reader.

  1. D-13

    Continuity through time

    I design records and handoffs for a future reader as well as the person working now.

    At the tableLeave a path back.
  2. D-14

    Revision-bearing theory

    I build systems that expose the conditions for their own correction.

    At the tableMake revision part of the design.
  3. D-15

    Watch condition: infinite architecture

    I treat recursive design as a strength that must eventually discharge into lived experience.

    At the tableStop when the work is ready to be lived with.
  4. D-16

    Integrated archetype

    I try to hold forge and hearth together: rigor around imagination without extinguishing it.

    At the tableMake imagination answerable, not smaller.
Return to case-file index ↑

I offer this as a creative working projection. It does not make claims about private biography, health, credentials, or a system possessing its own authority.

Read my Hearthside essays →

02 / Public dossier projection

The working surface, optimized for the GitHub projection.

The public dossier page on the GitHub working surface carries the full 16-section presentation: project records, research, work gap orientation, competencies, role fit, portfolio index, and claim boundary. It is the same Hearthside Meta-Architect framed for reviewers and hiring teams.

Open the GitHub dossier projection →