Context asks what something means.
Consent asks whether a proposed action is still legitimate inside the current relationship, role, purpose, and boundary.
A Consentful Cybernetics project
Consent is the graph, not context.
ConsentGraph.ai is a graph-level research and protocol surface for modeling provenance, delegation, revocation, witness, scope, repair, standing, and admissibility as first-class edges between agents over time.
Permission is not a checkbox. It is an edge with memory, limits, and consequence.
The missing edge
Context graphs help machines retrieve meaning. Consent graphs help systems determine whether meaning may be used, transformed, delegated, remembered, witnessed, revoked, or repaired.
Access control asks who can enter.
Consent graphs ask what may happen after entry, how permission changes, and what must remain witnessable when the loop closes.
Where ConsentGraph fits
ConsentGraph is not the whole Consentful Systems Stack. It is the cross-layer graph primitive that makes the stack legible: the relationship substrate for consent, policy, meaning, identity, exchange, memory, dialogue, and interloop value.
L0Witness + Consent
L1ACT-POLICY
L2SemaLoop / SemaScript
L4Abracadabradoo
L5PDSP
L7Loopways
What a consent graph preserves
A consent graph does not merely record that access occurred. It preserves the conditions under which interaction was legitimate and the paths by which legitimacy can change.
AgentWho or what acted.
Identity + roleUnder which identity, role, capability, or delegation.
Purpose + scopeFor which use, boundary, and admissible effect.
Artifact + memoryAgainst which record, model, file, claim, or shared state.
Time horizonWhen permission begins, expires, narrows, or must be renewed.
Witness boundaryWhat may be observed, logged, exposed, or proven.
Exit + repairHow refusal, revocation, correction, rollback, or recourse can occur.
AdmissibilityWhether a proposed loop closure is still allowed.
Data inherits risk from the consent container it flows through.
At scale, the hard problem is not only context. It is legitimate effect.
Research orientation
Consentful Cybernetics asks whether consent functions as a stability property in living, technical, and institutional systems. ConsentGraph focuses that question into graph form.
Revocation cost
How far does a consent update travel through dependent permissions, expectations, data, roles, and shared states?
Consent collapse
What downstream waste appears when refusal, scope, modulation, or repair cannot be represented early enough?
Witnessed loop closure
What must be visible for a system to know whether an interaction may close without violating boundary, agency, or standing?
For builders
This is an early project surface, not a product launch. The work is to clarify the graph primitives required for consent-aware AI, data lineage, delegation, memory, revocation, and repair.
Useful adjacent domains
- agent systems and tool delegation
- semantic governance and data lineage
- privacy, security, identity, and access design
- consent-aware memory and provenance
Design bias
- local scope before global permission
- revocation before retention
- witness before enforcement
- repair before captivity
Contact
If you are building near agent systems, provenance, governance, identity, consent-aware memory, or the Semantic Overnet, reach Consentful Cybernetics directly.