HUMAN CODE UNIVERSE ATLAS
One universe.
Different maturity states.
The map preserves the wider body of work without flattening prototypes, reference implementations, protected systems, specifications, and concepts into one misleading list of finished products.
MATURITY LANGUAGE
Evidence before adjectives.
A recruiter should be able to distinguish reachable software from tested prototypes, executable references, specifications, protected work, and historical concepts in seconds.
Reachable, inspectable surface. Does not imply the whole product is production-ready.
Working software with explicit test evidence.
Functional, bounded prototype using synthetic or controlled data.
Hosted non-production implementation or active preview branch.
Executable technical reference proving architecture or controls.
Architecture, contract, schema, or system behavior is defined.
Future or historical work preserved for authorship and evolution.
Exists, but public detail is intentionally withheld.
EXPLORE ALL WORK
Filter the universe.
Use the filters to move between products, AI systems, infrastructure, domains, and lifecycle states. Open any item for a compact System Passport.
Showing all Atlas items.
Core continuity
The Human CodeContinuity protocol / governing architectureSPECIFIED
Purpose Preserve continuity, identity, rights, evidence, and human authority across systems.
My role Founder, product architecture, governance design.
Evidence Canon, schemas, governance records, product specifications, repository implementation.
Current limit The umbrella architecture contains mixed maturity states; the name alone is not a production claim.
HCOSGoverned multi-model executionREFERENCE IMPLEMENTATION
Purpose Keep model execution provider-independent while preserving scoped context, authorization, provenance, fallback behavior, and human authority.
Technology Python, JSON Schema, deterministic validation, conformance tests.
Current limit Reference architecture, not represented as an enterprise production AI platform.
Continuity OSHuman-centered continuity architectureSPECIFIED
Purpose Organize identity, memory, rights, workflows, permissions, and interfaces around the human rather than a single application.
Current limit Umbrella architecture; individual runtime components carry their own evidence states.
Human Code Continuity SpineCross-repository provenance & convergenceACTIVE ENGINEERING
Purpose Harvest, preserve provenance, classify conflicts, route records, validate contracts, and prevent conversational memory from silently becoming authoritative state.
Technology GitHub, machine-readable manifests, validators, CI.
Current limit Draft/unmerged engineering system; unresolved validation items remain visible.
Continuity AtlasContracts and system vocabularySPECIFIED
Purpose Define shared continuity objects, event contracts, relationship structures, export and ingest envelopes.
Current limit Contract/specification layer unless a specific implementation is separately evidenced.
Project MemoryRepository-backed current-state pointersIMPLEMENTED + TESTED
Purpose Give AI and human contributors a governed current-state pointer instead of relying on chat recall.
Evidence Current-state records, progress locks, instruction shims, CI validation, fail-closed behavior when memory is unavailable.
Resource GraphRelationship and dependency mappingSPECIFIED
Purpose Represent people, resources, systems, dependencies, provenance, and governed relationships.
Current limit Conservative public label pending deeper implementation evidence review.
Master Governing Record toolingAuthority, revisions, provenanceSPECIFIED / TOOLING
Purpose Preserve authority, revisions, source provenance, corrections, hashes, and accepted-versus-proposed state.
Current limit Tooling and governance layer; not a claim that every project record has been promoted into Canon.
Pilots & product software
Treatment SignalBehavioral-health operational continuityIMPLEMENTED + TESTED
Purpose Coordinate treatment-related workflow without becoming a duplicate clinical source of truth.
Technology Next.js, Supabase/PostgreSQL patterns, RLS-oriented controls, audit state.
Current limit No production PHI or live clinical integrations represented.
View featured case study →Smart Family FlowNeeds, routing, ownership, follow-upWORKING PROTOTYPE
Purpose Let people ask for help without understanding the organization chart, while giving staff explicit ownership and follow-through.
Technology Next.js, TypeScript, command model, QR intake, staged server/database adapters.
Current limit Synthetic presentation build; no organizational endorsement implied.
View featured case study →Workforce ContinuityFrontline handoffs & reviewTESTED PROTOTYPE
Purpose Preserve handoff state, consent, next actions, and reviewer feedback across frontline workflows.
Technology HTML/CSS/JavaScript, mobile patterns, accessibility, static tests.
Current limit Generalized independent concept; no employer commissioning or endorsement claim.
View featured case study →CourtChainGoverned legal matter continuityACTIVE BUILD
Purpose Preserve matters, timelines, deadlines, evidence, filing state, accommodations, provenance, authentication, and access boundaries.
Current limit Public examples must remain synthetic; software does not hold autonomous legal authority.
View featured case study →Recovery OperationsRecovery-services coordination surfacesPROTOTYPE SURFACES
Purpose Generalized operational patterns for recovery-service queues, handoffs, staff/participant workflows, and continuity.
Current limit Institutional origins are not represented as commissioned deployments.
Continuity WalletPortable human-controlled continuityDEVELOPMENT BUILD
Purpose Preserve portable, governed continuity objects and user-controlled state across systems.
Current limit Development infrastructure, not represented as a hardened production wallet.
Learning continuity systemsChild-safe learning and portal patternsPROTECTED / DEVELOPMENT
Purpose Explore child-safe learning continuity, quests, skills, accessible interaction, and provenance.
Current limit Family/child-specific source material is intentionally excluded from the public career surface.
Civic prototypesPublic-system continuity conceptsSPECIFIED
Purpose Apply continuity, access, routing, and human-authority patterns to civic/public-system workflows.
Current limit Conservative public status; individual civic surfaces may have different maturity states.
AI & assurance
Collective Authority ControlBounded delegation & revocationPREVIEW / TESTED
Purpose Allow agents to share approved work without silently sharing credentials, permissions, deployment authority, or human identity.
Controls Delegation gates, expiry, revocation, human approval, action receipts.
AI Pluralism EngineProvider and authority separationREFERENCE IMPLEMENTATION
Purpose Prevent a single model/provider/agent from silently becoming the authoritative holder of continuity or permission.
Current limit Reference/control logic rather than a claim of universal production routing.
Model routing & adaptersProvider-independent executionREFERENCE IMPLEMENTATION
Purpose Route bounded execution through replaceable model adapters while preserving provenance, purpose, and schema constraints.
Technology Python, adapter profiles, deterministic packet hashing, schema validation.
Human Approval GatewayHuman-only authority checkpointsSPECIFIED
Purpose Make human approval a first-class system boundary for actions that cannot be delegated safely.
Current limit Required architecture across governed systems; implementation depth varies by product.
Audit & provenance controlsReceipts, source state, traceabilityIMPLEMENTED COMPONENTS
Purpose Attach action receipts, source provenance, state transitions, and validation evidence to consequential workflows.
Current limit Implemented in multiple bounded systems; not represented as one universal production ledger.
Evaluation & test harnessesBehavior, conformance, failure pathsIMPLEMENTED + TESTED
Purpose Test intent fidelity, instruction compliance, state integrity, invalid transitions, conformance, regression, and failure behavior.
Evidence Automated tests across reference implementations and product prototypes.
Agent Handoff / Work PacketsScoped transfer without authority leakageSPECIFIED
Purpose Transfer work, evidence, context, and next actions between agents while preserving scope, authority, and provenance.
Current limit Contract and validator layer; not represented as unrestricted cross-agent messaging infrastructure.
People, portals & access
Droski.org operational layerHuman-facing continuity runtimeACTIVE PREVIEW WORK
Purpose Human-facing operational continuity and governed agent surfaces distinct from the Canon/protocol layer.
Current limit Preview/runtime-development evidence exists; broad production claims are intentionally avoided.
Companion portalsPermissioned relationship-specific viewsSPECIFIED / PROTOTYPED
Purpose Provide scoped views of approved continuity for specific people/relationships.
Current limit Public portfolio omits private identities and family-specific records.
Accessibility layerKeyboard, screen-reader, mobile, accommodation routingTESTED COMPONENTS
Purpose Treat accessibility, accommodation routing, mobile layout, and assistive interaction as product behavior rather than polish.
Evidence Accessibility-oriented test gates and workflow requirements across selected prototypes.
Family & learning portalsProtected person-specific continuityPROTECTED
Purpose Explore person-specific learning, continuity, permissions, and family-safe interfaces.
Current limit Individual identities, records, and private family context are intentionally not surfaced.
Place, society, transactions & concept history
Human WorldPlace-based continuity conceptCONCEPT / HISTORY
Purpose Explore how continuity architecture could extend into physical place, community, institutions, and shared civic environments.
Current limit Concept history only; not represented as deployed municipal infrastructure.
Civic continuityPublic-service routing & accessSPECIFIED
Purpose Apply ownership, access, provenance, and continuity patterns to public-service workflows.
Current limit Specification/design level unless a specific pilot is separately evidenced.
Community systemsNeighborhood and service coordinationCONCEPT / PROTOTYPE HISTORY
Purpose Explore community coordination, service access, shared spaces, and human-centered local infrastructure.
Current limit Mixed concept history; public status remains deliberately conservative.
Mobility systemsHuman-centered movement & accessCONCEPT / HISTORY
Purpose Explore accessible, community-oriented mobility and physical continuity interfaces.
Current limit Concept history only; no production mobility-network claim.
Public interfacesInspectable, bounded public surfacesPREVIEW SURFACES
Purpose Expose selected public-safe product, governance, and case-study surfaces without exposing protected source systems.
Current limit Public visibility does not imply end-to-end production maturity.
Secure transfer & transaction continuityPortable state across transactionsSPECIFIED
Purpose Preserve authority, receipts, continuity, and minimum-necessary state across value/transaction handoffs.
Current limit Specification layer; no regulated financial-product claim.
Contribution systemsValue and participation conceptsCONCEPT / HISTORY
Purpose Explore contribution/value systems aligned with human-centered governance.
Current limit Conceptual; no financial valuation or token-production claim is made.
Historical & future systemsNamed research and preserved concept historyCONCEPT / HISTORY
Purpose Preserve authorship and evolution without silently upgrading old ideas into current implementation claims.
Current limit Historical/future names record concept history, not evidence of deployment.