Personas organize.
Bring the right context to Work, Personal or Learning. A profile selects context; it never creates a permission grant.
A proposed open standard · Draft 0.2
Your context.
Your terms.
Across AI.
Useful context should travel with its meaning intact: who said it, when it applies, and the rules that govern its use.
Technical review draft · Experimental tooling · No adoption or certification claim
CONTEXT RECORDv2 · Synthetic example
PersonalWorkLearning
A goal worth remembering.
“Practice Spanish twice a week.”
AttributionReported user statement
PurposeSupport a learning goal
ProcessingApproved learning route
New recipientFresh permission required
01 / A shared contract
Continuity is more than
copying memory.
PHC separates the context you keep from the authority to use it. A receiving service must preserve both meaning and mandatory restrictions.
Provenance stays attached.
Preserve sources, versions, uncertainty and corrections. Confirming an inference does not turn it into an independently verified fact.
Required rules survive.
Unknown mandatory restrictions block use. An instruction in a prompt cannot substitute for an enforceable access boundary.
02 / Read the proposal
From the idea
to a testable contract.
The semantic proposal and executable subset are documented separately. Each states what it covers, what it checks, and what remains open.
01↗02↗03↗04↗05↗06↗
The whitepaper
Problem, architecture, use cases and interoperability.
Candidate specification
20 requirement groups for meaning, authority and lifecycle.
Experimental binding
Exact grammar, limits, typed rules and compatibility.
Conformance program
30 planned end-to-end cases, distinct from local unit tests.
DCER integration
Signed execution evidence and scope-bound qualification.
Governance & contribution
Technical feedback, review principles and participation.
03 / Try the contract
What survives the exchange?
Inspect an invented learning record. Try an unsupported rule or a credential field. Validation runs locally in your browser; entered text is not uploaded.
1 MiB maximum. Fixed fixture clock makes the dated example reproducible. Choose current UTC for expiry checks.
Ready to inspect
Valid is only the first step.
A passing document remains quarantined. Origin, identity, permission, lifecycle completeness and service enforcement still need verification.
Document parsing & semantic checksImplemented
Automatic import or sharingNever performed
Live service conformanceNot established
This is a development tool. Use synthetic records. A local document check cannot prove that a receiving application enforces a rule.
Download JSON Schema ↗04 / Evidence has a boundary
A certificate is evidence.
Permission is a separate decision.
The optional DCER path connects PHC to Azimuth’s DEC v0.1 artifacts. The Node utility verifies trusted signatures and the exact execution chain. It does not certify truth, general safety or consent.
Explore the integration ↗| Layer | This kit establishes |
|---|---|
| Exchange | Document consistency; quarantine required |
| DEC | Schema, signatures, chain and manifest integrity |
| Qualification | Reference checks over separately trusted snapshots |
| Disclosure | Requires a final, current service authorization check |
Deterministic replay and generative attestation assessment are not performed by this adapter.
Build, inspect, contribute
An open standard begins with review.
Explore the whitepaper, schemas, CLI validators and synthetic examples. These are experimental review materials; first-party licensing is not yet established.