Know what is missing.
Documents and requirements should stay connected to the specific housing journey instead of becoming a pile of files with no obvious next action.
HOMEKEY · SPECIFIED PROPOSAL
Keep a housing journey from falling apart between systems.
HomeKey is a Human Code housing-continuity proposal for keeping applications, documents, eligibility, appointments, deadlines, approvals, missing items, and next steps connected around the person.
Maturity: SPECIFIED. This page presents a designed proposal. It is not a claim that HomeKey is deployed, purchased, adopted, or operating inside a housing agency.
HOMEthe human journey
Apply
Documents
Deadline
Next step
Support
Proof
THE PROBLEM
Housing work is already hard. Fragmented systems make it harder.
A person can interact with applications, documents, eligibility rules, appointments, notices, staff, providers, and deadlines that live in different places. When the handoff breaks, the person often becomes the only one holding the whole story together.
Know who owns the next step.
The person should be able to understand whether the next move is theirs, a support worker’s, a reviewer’s, or another system’s.
Keep going after a handoff.
Changing staff, organizations, or software should not erase the context needed to continue the journey.
WHAT HOMEKEY WOULD PRESERVE
The useful thread around the housing process.
The proposal is continuity around existing housing processes, not a replacement for authoritative eligibility, housing, benefits, or agency systems.
Where am I?
Keep the current application or housing goal understandable.
What is missing?
Connect required documents, unresolved questions, and due dates.
Who goes next?
Make the receiving lane and expected follow-up visible.
What already happened?
Preserve a readable record so the person does not have to reconstruct every prior step.
BOUNDARY
A concept can be useful without pretending it is already deployed.
HomeKey is currently represented as a specified Human Code proposal. Any future implementation would still need authoritative housing-domain sources, privacy and accessibility review, security testing, representative user validation, and explicit deployment authorization.
No adoption claim
This public concept does not represent a housing agency, government program, customer, procurement decision, or institutional endorsement.
No universal record
Housing, benefits, healthcare, legal, and family systems keep their own authority and privacy boundaries.
No hidden authority
A continuity layer should not invent eligibility decisions, approvals, deadlines, or staff actions that have not been verified.
START WITH THE JOURNEY
See what housing continuity looks like from the person’s side.
The public Human Code walkthrough shows the idea in plain language before the technical architecture.