01Research program
Typed Context & Control Protocol
Typed representations, context conditions, interaction compilation, and explicit proof obligations.
Research architecture · public guide · evaluation instrumentsH+C / 03Portfolio
I use the portfolio as a trail, not a trophy case.
This is where research programs, knowledge architecture, software, publication, and design meet without hiding the posture or limits of each body of work.
Browse selected workFrom my workbench
Hearthside thought projection · review requestedI use the portfolio as a trail, not a trophy case.Read the working archetype →The useful story is how research becomes an artifact, how the artifact is checked, and where the work remains provisional or unfinished.
01 / Selected work
Six bodies of work, presented with their boundaries intact.
I use this portfolio to show how inquiry becomes a program, artifact, software surface, method, or public record—not to manufacture case-study outcomes.
02Knowledge architecture
EKRP
A source-governed application profile for human-readable knowledge representation, provenance, and review.
Semantic documents · evidence packets · standards crosswalks03Software system
Exocore
A local-first systems direction connecting agents, knowledge, governance, observability, and human return.
Rust services · TypeScript interfaces · operational boundaries04Methods practice
Prompt & Context Atlas
Technique-level practice for prompts, context selection, tool boundaries, evaluation, and revision.
35 field cards · prompt scaffolds · failure-mode checks05Publication
Field Journal
Long-form research notes, essays, and technical writing with visible claim and source context.
Research essays · technical articles · correction path06Research communication
Ember Circuit
A warm technical visual language for making complex system boundaries and evidence states legible.
Visual grammar · research figures · interface foundationsResearch horizon / eight product candidates
Distinct experiences. One governed substrate.
These are review-required product candidates collected from the Hub portfolio. They are directions under study—not released applications, subscriptions, or proof of efficacy.
- P-01Internal keystone candidate
TCCP Protocol Forge
Compile bounded goals, sources, constraints, and effect policy into inspectable typed workflows.
Desktop + web workbenchReview required · not active - P-02Recommended public proof
Ember Evidence Loom
Build question-bounded claim and evidence maps across source revisions and disputes.
Web service + desktop readerReview required · not active - P-03Individual-tool candidate
Exocore Living Atlas
Observe one bounded project or system through source-linked snapshots and change.
Local-first desktopReview required · not active - P-04Partnered research
Hearth Commons Chamber
Help groups examine proposals, evidence, objections, and accountable decisions.
Civic web serviceReview required · not active - P-05First vertical candidate
Learning Foundry
Turn explicit learning goals into inspectable practice, evidence, feedback, and revision.
Web + desktop studioReview required · not active - P-06Synthetic-only research
Care Relay Lab
Study fictional coordination handoffs and information loss without clinical operation.
Desktop simulation labReview required · not active - P-07Partnered research
Resilience Maproom
Map observations, dependencies, scenarios, and community knowledge with visible uncertainty.
Geospatial web serviceReview required · not active - P-08Expression-layer candidate
Ember Symbolic Studio
Compose source-linked prose, diagrams, notation, and bilingual symbolic editions.
Creative desktop applicationReview required · not active
03 / Practice behind the portfolio
The work is connected by a way of seeing.
The Hearthside Meta-Architect dossier describes the practice without turning private context into a public claim.
Open my working dossier →