PHC governance and participation
Technical review draft · 15 October 2026
EngramForge maintains Portable Human Context. PHC is a proposed standard under technical review, with experimental validator utilities. It is not an adopted standard, an independently governed standards organization or a certification program.
The proposal is intended for implementation across services. Its semantics should not depend on a particular operator, product or hosting provider. Participation does not confer rights over another person's context.
Technical feedback
Send specification questions, interoperability findings and research feedback to research@engramforge.com. Include the document version, affected requirement IDs, the problem and a synthetic example. For other questions, see Contact.
Useful feedback describes compatibility impact, expected behavior and failure cases. Please do not send personal context, credentials or confidential third-party material. Consult the draft status before submitting code or other material for incorporation; contribution and first-party licensing terms are not yet established.
Reviewing changes
Editorial changes improve clarity without changing required behavior. A change that affects an allow/deny result, mandatory restriction, interpretation or cryptographic byte representation requires substantive compatibility review.
Substantive proposals should include:
- A problem statement and the affected requirements, schemas and examples.
- Expected behavior, negative cases and migration or loss analysis.
- Security and privacy implications, including effects on existing restrictions.
- Evidence scoped to the exact implementation and version tested.
Reviewers should disclose relevant affiliations and conflicts. Evidence supplied by an implementer must be identified as such; it is not independent review. The conformance plan defines the proposed evidence and failure conditions.
Releases and claims
Published bindings should identify their version, compatibility boundaries and limitations. Unknown mandatory semantics must remain blocked. A schema check, signature check or unit-test result must not be presented as service certification, independent interoperability or consent.
Current materials are review drafts. Formal governance, contribution terms and any future conformance program will be documented before claims are made under them. See Draft status for the current scope and licensing status.
Security and privacy reports
For a suspected vulnerability, contact support@engramforge.com with a minimal description and a synthetic reproduction. Ask for an appropriate private transfer method before sending sensitive evidence. Privacy questions go to privacy@engramforge.com. No response-time or independent-audit guarantee is made by this draft.