HEARTH & CODE / PUBLIC ORIENTATION
Make the work
legible.
A studio for thinking, building and creating with AI—where methods are explicit, examples are inspectable, and the limits of a claim stay visible.
FIRST STEP
Find your starting point.
Every visitor arrives with a different question. Choose the route that matches what you need today.
HOW TO USE THIS SITE
Choose by what you need to do.
I'm new here — what is this?
Start with the orientation and working posture. What a source-aware studio means and how the site is organized.
→I need a technique I can test right now.
Fieldcraft has 32 runnable field notes with examples, counterexamples and source links. Engineering, knowledge, creative work.
→I want the method behind the techniques.
Bind, make, check, return. The working cycle that connects every practice area with explicit limits on each step.
→I need a prompt method, not a magic string.
128 retained prompt methods organized by transformation. Purpose, input shape, failure mode, evaluator.
→I want to trace a claim to its source.
Source identity, evidence vs claim, absence vs contradiction, synthesis with dissent, projection loss records.
→I want to understand reliable system design.
Typed boundaries, lifecycle states, hold-indeterminate patterns, local proofs before runtime. Candidate architecture.
→I want to see how all the disciplines connect.
Architecture, engineering, design and creative work as a weave. Each keeps its own criteria and failure modes.
→I want to evaluate a full public portfolio.
Complete public dossier and portfolio framed around the Hearthside Meta-Architect archetype. Project records, competencies, work history, and career orientation.
THE ORIENTATION MAP
Eight surfaces, one shared practice.
Each points to active work, source material or a public method. Candidate work stays marked as candidate work. Detail pages share a consistent information architecture: concept → technique → example → boundary → next route.
IDENTITY
Hearth & Code
A source-aware studio for agentic engineering, knowledge work, software design and creative practice. Each area has distinct inputs, evidence and failure modes.
12 sections — studio posture, claim boundaries, practice areas, return discipline, starting guidance, site organization, creative practice
OPEN THE ORIENTATION ↗ 02METHOD LIBRARY
Fieldcraft
32 precise, runnable field notes for prompt craft, synthesis, reliable systems, Rust and creative work.
EXPLORE THE LIBRARY ↗ 03PRACTICE
Work & studio
Architecture, design, development and research as connected practices with distinct responsibilities. Each has recoverable and unrecoverable failure modes.
12 sections — architecture, engineering, design, creative work, weave interaction, recovery, tool choice, knowledge work
OPEN THE STUDIO ↗ 04FOUNDATION
Methodology
Start with the source. State the boundary. Make the check visible. Return a result with its limits intact.
15 sections — bind, make, check, return, loop dynamics, notation guide, research framing, source ledger, claim mapping
OPEN THE METHOD ↗ 05PROMPT CRAFT
Prompt engineering catalog
128 retained methods and a 512-method horizon. Organized by transformation, not topic. Each method has purpose, preconditions, prompt shape, failure mode and evaluator.
3 sections + 128 entries — compact intro then interactive grid with filters and animated reflow
OPEN THE CATALOG ↗ 06KNOWLEDGE WORK
Knowledge & evidence
Trace claims to sources, preserve dissent, distinguish absence from contradiction, and report loss in every projection.
12 sections — source identity, claims vs evidence, absence vs contradiction, review records, synthesis with dissent, projection loss, counterevidence methodology
OPEN THE EVIDENCE LAYER ↗ 07ENGINEERING
Engineering & Exocore
Rust, lifecycle design, typed boundaries and recoverable systems. Public material describes techniques and candidates, not a running service.
13 sections — meaning vs mechanics, typed boundaries, hold-indeterminate, local proofs, idempotency contracts, fail-closed, lifecycle state machine, contract anatomy, modularity practice
OPEN THE ARCHITECTURE ↗ 08PORTFOLIO
Portfolio & Dossier
Complete public portfolio and career dossier framed around the Hearthside Meta-Architect archetype. Project records, competencies, work history, and career orientation.
16 sections — archetype orientation, project records (Hearth & Code, Prompt Atlas, Exocore, Fieldcraft, Knowledge Hub), research, work gap, background, competencies, style, role fit, portfolio index
OPEN THE PORTFOLIO ↗EVIDENCE CLASSES
Every page labels its claims.
The same eight epistemic labels appear throughout the site. They signal what kind of claim is being made and prevent a passing check from being mistaken for a final verdict.
SOURCE
A named, versioned artifact that the claim depends on — a specification, a charter, a committed document.
EVIDENCE
An observed result from a direct check or measurement — build output, test result, rendered page.
INFERENCE
A reasoned conclusion from evidence with visible assumptions — patterns drawn from observed practice.
HYPOTHESIS
A testable explanation with alternatives and a possible falsifier — ideas that are explicitly provisional.
PROPOSAL
A candidate artifact or design awaiting disposition — drafts, designs, recommendations.
PROJECTION
A derived view that does not replace its source — dashboards, summaries, rendered pages.
RECEIPT
Bounded process history — what happened, not what it authorizes for the future.
UNKNOWN
Cannot be reliably classified — a gap shown as a gap, not hidden.
THE OPERATING POSTURE
A useful answer carries its own boundaries.
- 01Bind
Use a direct source, a declared task and a clear owner. Know what the work is answering and what it cannot change.
- 02Make
Produce a small, inspectable artifact with a working seam. Let its promises be small enough to test.
- 03Check
Test the stated predicate independently of fluent explanation. Include the counterexample that keeps the claim honest.
- 04Return
Keep evidence, inference, proposal and release distinct. A useful return names the next question as clearly as it names what was done.
CLAIM BOUNDARY
What this site does not assert.
- No page in this orientation asserts verification, product completion, operational deployment, provider availability or third-party adoption.
- Candidate and proposal labels mark material that has not been accepted, released or verified.
- Synthesized examples demonstrate a method; they do not trace to a releasable source record and should not be cited as empirical evidence.
- Site content describes working approaches and candidate designs. It does not constitute a binding standard, a governance implementation or a warranty of fitness for any purpose.
- Readers evaluating any technique for their own work should independently verify that it meets their requirements, constraints and safety needs.