PEDRO CASTAÑEDA · HUMAN CODE

Systems for the
human in the loop.

AI product, continuity architecture, governed execution, public systems, accessibility, and release engineering — built from the messy realities where software, institutions, and people collide.

The master résumé is the most recent condensed résumé modification; the recruiter view is a bounded fast-read projection of the same evidence.

GREATER BOSTON2023—2026PUBLIC-SAFE CAREER EVIDENCE
HUMANCONTINUITYIDENTITY · AUTHORITY · EVIDENCE
01IDENTITY 02AUTHORITY 03CONSENT 04HC-GIF 05RECEIPT 06MEMORY 07PORTABILITY
LIVE ARCHITECTURE MAPPUBLIC TOPOLOGY ≠ CANON
06selected system portraits
—sourced model milestones
—public-safe feature records
05interactive evidence lenses

SELECTED SYSTEMS / 01—06

Not project cards.
Working systems with edges.

Each portrait is a different projection of the same operating thesis: preserve the human, preserve authority, make state visible, and make the software prove what happened.

PROGRESSION / SYSTEMS ATLAS

Watch the architecture
become a universe.

The portfolio is not a museum of screenshots. It is a living map of problems → ideas → products → primitives → evidence.

MODEL ECOSYSTEM
HUMAN CODE

HIRING SIGNAL / SAME EVIDENCE

Product judgment.
Systems depth.
Shipping discipline.

The same body of work can be read through different roles without inventing different versions of the career record.

30-second recruiter read
01

AI Product

Workflow discovery, product framing, human authority, cross-domain systems.

02

Technical PM

State contracts, auth, routing, release gates, cross-functional execution.

03

Product Engineer

JavaScript/TypeScript, Supabase/Postgres, UI state, browsers, accessibility, shipping.

04

AI Systems

Provider routing, policy, receipts, memory boundaries, local execution.

05

Solutions Architecture

Integration boundaries, source-of-truth separation, portability, deployment.

06

Human-Centered AI

Consent, accessibility, provenance, human review, minimum-necessary context.

THE OPERATING LANGUAGE

Human Code operating distinctions

IDENTITY ≠ AUTHORITYEXECUTED ≠ RETAINEDDRAFT ≠ PUBLISHEDDEPLOYED ≠ WORKINGCHRONOLOGY ≠ CAUSATION
01

Human authority stays explicit.

Capability, consensus, access, and communication do not manufacture permission.

02

Evidence stays attached.

Consequential claims should point back to source, state, revision, or runtime proof.

03

Models stay replaceable.

Identity, durable memory, and continuity are not allowed to disappear with a provider.

LET'S BUILD SOMETHING THAT HOLDS UP

Complex human workflow?
Good.

If the problem touches product, AI, messy operations, evidence, governance, accessibility, or continuity, that is the kind of edge I like working on.

founder@thehumancode.tech