Portfolio & Dossier

Archetype orientation: Hearthside Meta-Architect

The Hearthside Meta-Architect builds workshops rather than opaque machines — systems people can enter, operate, correct, and return to. Its emblem is the hearthside workbench: warmth without softness, structure without surveillance, invitation without coercion.

The mission is to build conditions under which people, tools, agents, and knowledge can work together without quietly erasing agency. This means preferring systems that preserve provenance, semantic ownership, state, uncertainty, and a route back into the work.

This archetype is not a job title or a credential. It is a stance toward systems, and it shapes how every project in this portfolio is designed, scoped, and presented.

Project record: Hearth & Code

Role: Creator, architect, and sole developer Public URL: https://hearthandcode.github.io/ Status: Active public surface

Hearth & Code is a source-aware studio for thinking, building and creating with AI. It spans: - A public orientation site with 7 detail pages and 32 runnable Fieldcraft articles - A 128-entry interactive prompt engineering catalog drawn from a 512-record research atlas - A visual system (Ember Circuit) and editorial contract that governs public-safety boundaries - Fieldcraft: 32 practical field notes pairing a precise idea with a working example, counterexample, and explicit claim limits

Relevant skills: Static-site engineering, information architecture, prompt engineering, knowledge engineering, public-safety governance, visual system design.

Project record: Prompt Technique Atlas

Role: Architect and researcher Status: Active research corpus (512 records, 64 categories, 16 documents) Public surface: https://hearthandcode.github.io/prompt-catalog.html

The Prompt Technique Atlas is a structured corpus of 512 distinct prompt engineering techniques organized across 64 categories and 16 documents. Each technique record includes mechanism, trigger, input/output contract, failure modes, evidence class, and governance boundaries. 128 techniques are projected publicly in the interactive catalog.

Relevant skills: Knowledge engineering, structured taxonomy design, controlled vocabulary development, research synthesis, evidence classification.

Project record: Exocore (candidate architecture)

Role: Architect and researcher Status: Candidate architecture — described on the engineering page at https://hearthandcode.github.io/engineering-exocore.html

Exocore is a candidate architecture for local-first, contract-bound product modules. Its principles include: typed boundaries between modules, explicit lifecycle states with legal transitions, hold-indeterminate patterns for uncertain operations, local proofs before runtime, idempotency as contract design, and fail-closed recovery.

The architecture is documented as public pedagogical material describing design principles and synthetic patterns — it does not represent a running service or released product.

Relevant skills: Systems architecture, lifecycle design, contract-first development, state machine design, distributed systems patterns.

Project record: Fieldcraft corpus

Role: Author and researcher Status: Public — 32 articles at https://hearthandcode.github.io/fieldcraft.html

Fieldcraft is a 32-article library of practical techniques covering engineering, knowledge, and creative work with AI. Each article follows a disciplined structure: state the predicate, give a bounded task, run an independent check, try the counterexample, and keep the claim bounded. All articles include working examples (Node.js, Python, and Rust where applicable) with 111 verified fixture checks.

Articles span prompt craft, reliable systems, Rust development, knowledge engineering, creative direction, and governance. Each has a source-bound formulation, a runnable demonstration, and an explicit claim limit.

Relevant skills: Technical writing, software engineering, documentation architecture, fixture-based validation.

Project record: Hearth & Code knowledge architecture

Role: Architect and sole knowledge engineer Status: Active Hub infrastructure

The Knowledge Hub is a local-first, source-bound governance substrate for knowledge engineering, agentic profile work, and evidence-centered research. It implements ESS (Exocore Sigil Standard) for artifact classification, lifecycle management, provenance, and review-state transitions.

Key structural components: 32 Core32 profile contracts, EKRP module records, RFC legislative catalogs, bounded I/O type systems, persistent context contracts, and reproducible validation harnesses. The hub governs 16 wings with 256 workrooms using a sequential naming registry.

Relevant skills: Knowledge engineering, information architecture, governance system design, taxonomy development, agent runtime context engineering.

Research: Self-directed PhD in Applied AI

Role: Primary researcher, developer, and subject Status: Active — autoethnographic research program

Scott Rallya is pursuing a self-directed PhD in Applied AI using autoethnographic methodology — an N=1 study of his own practice as an AI engineer and neurodivergent learner. The research examines how structured cognitive scaffolding, agentic tooling, and source-bound knowledge systems affect working capacity, continuity, and agency.

Public research outputs include the Fieldcraft corpus (methodological foundation), the Prompt Technique Atlas (structured evidence of technique design), and the Hearthside architecture (design principles derived from observed practice).

Relevant skills: Autoethnographic methodology, research design, qualitative methods, cognitive science applied to AI tooling.

Work gap orientation

Career context: Scott Rallya's professional experience spans fintech, healthcare, telecom, consulting, and infrastructure — forward-deployed engineering, systems architecture, and technical leadership across complex regulated environments. The most recent continuous employment period was followed by a career gap related to a personal health decision.

Gap framing: The gap was driven by the need to address a long-standing medical condition whose management was incompatible with sustained full-time employment at that time. The decision to step away was deliberate and therapeutic — not a failure of performance or employability.

Bridge to current work: During this gap, Scott built the entire Hearth & Code ecosystem — the Knowledge Hub, Fieldcraft corpus, Prompt Atlas, Exocore architecture, and public site — as both a research platform and a demonstration of sustained productive capacity. The work produced during this period is the strongest evidence of current capability: 32 published field notes, 512 documented techniques, a complete governance system, and a public-facing studio.

Clinical status: The condition that prompted the gap is now medically managed. The systems and practices developed during this period (cognitive scaffolding, structured work cycles, explicit recovery protocols) were designed partly as accommodations — and they have proven effective enough to sustain deep technical output across a multi-year research program.

What this means for an employer: The gap represents a resolved health event whose downstream result is a more experienced engineer with a proven adaptive capacity, a documented body of independently produced work, and systems designed explicitly for sustained high-quality output.

Professional background summary

Scott Rallya has worked across the full stack in environments ranging from early-stage startups to enterprise financial systems. His career spans:

• Fintech: Systems architecture, payment processing, compliance-oriented engineering
• Healthcare: Regulated data systems, interoperability, clinical workflow integration
• Telecom: Infrastructure engineering, distributed systems, operational reliability
• Consulting: Forward-deployed engineering, client-facing technical leadership
• Infrastructure: Platform engineering, developer tooling, system design

Role pattern: Scott consistently gravitates toward roles that combine deep technical work with architectural responsibility — designing systems and the conditions that make them reliable, comprehensible, and revisit-able.

Notable pattern: In every domain, Scott's contribution has included building the scaffolding around the core work: documentation, testing infrastructure, deployment pipelines, review processes. This is the Hearthside pattern before it had a name.

Technical competencies

Languages and runtimes: - Rust (systems programming, type-state design, contract-oriented development) - TypeScript/JavaScript (full-stack, tooling, automation) - Python (research tooling, knowledge engineering, automation) - Go (services, tooling) - Bash/Zsh (system-level automation, development environments)

Systems and infrastructure: - Linux system administration, Wayland compositor development (Smithay) - Cloudflare Workers, Durable Objects, Pages - Kubernetes, GitOps lifecycle - Tauri desktop application development - Hermes Agent runtime, multi-agent orchestration

Knowledge and research engineering: - Knowledge Hub architecture (ESS, EKRP, controlled vocabularies) - Prompt technique taxonomy design (64-category, 512-record atlas) - Autoethnographic research methodology - Source-bound governance and provenance systems - Agent runtime context engineering (Core32 profiles, SOUL contracts)

Design and creative: - Ember Circuit visual system (editorial serif, evidence-forward design) - Information architecture for complex systems - Technical writing and documentation design

Working style and team fit

Scott works best in environments where the work is understood as a craft with visible standards — not because he needs supervision, but because explicit standards make collaboration faster and more honest.

Communication: Direct, specific, source-aware. Scott writes the return before the goal when work is long-lived. He prefers an honest bounded claim to a flattering but unsupported characterization.

Collaboration: Scott produces best when given a bounded problem, a clear owner, and the authority to decide within that boundary. He pushes back when scope creeps without an explicit scoping decision, not because he avoids work, but because unmanaged scope produces unmanaged quality.

Independence: Scott has operated as a solo architect and developer throughout the Hearth & Code project, producing all 32 articles, 512 technique records, the full Hub governance system, and the public site without external oversight. This demonstrates the ability to sustain deep technical output over extended periods.

Remote readiness: Scott has worked remotely across multiple time zones and organizations. He is self-directed, asynchronous-friendly, and comfortable with written-first communication.

Role fit: where the Meta-Architect thrives

The Hearthside Meta-Architect is not a conventional IC or manager role. It is most effective where:

1. The problem space is ambiguous and the first job is to make it legible — understanding the shape of the work before optimizing it
2. Systems need to be designed for continuity, not just throughput — the work must survive handoff, interruption, and context loss
3. The boundary between human and tool needs deliberate architecture — agency-preserving design, not automation for its own sake
4. Provenance and evidence matter — claims need to trace to sources, decisions need receipts

Best-fit roles: Staff Engineer, Architect, Research Engineer, Technical Lead, Platform Engineer, Knowledge Engineer, Developer Experience Lead, Founding Engineer.

Less ideal fits: Roles requiring rapid context-switching across unrelated domains, roles where scope is defined entirely by others with no architectural input, or roles where the quality bar is determined by shipping speed rather than structural integrity.

Public portfolio index

This page is the single entry surface for Scott Rallya's public professional body of work. Every claim made here is traceable to a live public URL:

• Hearth & Code orientation: https://hearthandcode.github.io/ — the studio, method, and evidence of sustained output
• Fieldcraft library: https://hearthandcode.github.io/fieldcraft.html — 32 runnable field notes with fixture-verified examples
• Prompt engineering catalog: https://hearthandcode.github.io/prompt-catalog.html — 128 public technique records from a 512-record atlas
• Engineering & Exocore: https://hearthandcode.github.io/engineering-exocore.html — candidate architecture with typed boundaries and lifecycle states
• Methodology: https://hearthandcode.github.io/methodology.html — the Bind-Make-Check-Return working cycle
• Knowledge & Evidence: https://hearthandcode.github.io/knowledge-evidence.html — source binding, claim mapping, and evidence discipline
• Work & Studio: https://hearthandcode.github.io/work-studio.html — architecture, design, engineering, and creative work as connected practices

Additional records (candidate/pedagogical): Exocore architectural descriptions, Knowledge Hub governance records, Prompt Technique Atlas documentation.

Compensation and engagement posture

Compensation research methodology: Salary expectations are informed by market data from levels.fyi, Glassdoor, company disclosures, and recruiter ranges, cross-referenced by role level, geography, and industry. Research is maintained in a local evidence ledger with source and date.

Engagement types considered: - Full-time employment (preferred for deep integration into complex systems) - Contracting/consulting (for bounded architectural or research engagements) - Research collaboration (for academic or applied research partnerships)

Level expectation: Staff Engineer / Architect / Technical Lead equivalent — roles where system-level design decisions are the primary output.

Boundary: This page presents the public portfolio for evaluation. It does not submit applications, initiate outreach, or modify public profiles. Engagement discussions are conducted directly through the appropriate channels.

Claim boundary and sourcing

This dossier is a projection from the local evidence ledger maintained by the Employment Operations system. Each claim about projects, skills, or experience is supported by specific public project records that can be independently verified.

• Project URLs are live and inspectable
• Research claims (512-record atlas, 32 articles, 111 fixture checks) are verifiable from the public site
• Professional background descriptions are based on the candidate's attested experience
• The work gap description is stated at the level of explanation the candidate has authorized for public disclosure

Metrics: The Hearth & Code public site contains 41 published pages. The Fieldcraft corpus has 111 passing fixture checks and 31 executable Node examples. The Prompt Technique Atlas contains 512 records across 64 categories. The Knowledge Hub governs 16 wings with 256 workrooms.

What this page does not assert: It does not assert that any referenced project is a released product, deployed service, or independently verified system. It does not assert employment outcomes or hiring suitability beyond the evidence presented. It does not include personal contact information, medical records, or private correspondence.

Archetype return and next action

The Hearthside Meta-Architect archetype is offered as an orientation to Scott Rallya's body of work and the principles that guide it. If the framing resonates, the strongest next step is to evaluate the public work directly:

1. Browse the Hearth & Code orientation at https://hearthandcode.github.io/ — the most direct entry to the full scope of work
2. Inspect Fieldcraft articles at https://hearthandcode.github.io/fieldcraft.html — the methodological foundation in practice
3. Review the Engineering page at https://hearthandcode.github.io/engineering-exocore.html — architectural thinking in depth
4. Explore the Prompt catalog at https://hearthandcode.github.io/prompt-catalog.html — evidence of systematic knowledge work at scale

Next gate: Direct conversation through established professional channels. Scott Rallya is prepared to discuss any project, design decision, or architectural principle in depth.

Return: This dossier, its claims, and the evidence supporting them are all available for independent verification. The work speaks for itself — the archetype is an invitation to understand how it was made.