aeoess/solutions/Content

Terms that travel
with the bytes.

Sign your governance at the source. Every agent that reads the page can verify what is permitted, what is logged, and what revokes downstream. The chain from access to derivative is reconstructable from primitives.

Live primitivesApache-2.0

Life of an Action

One action, one signed receipt.

Content licensing turns on the action-receipt audit trail. Each access is a signed action; the receipt is the ledger entry.

Who this is for

Publishers, data providers, IP owners.

Your content is being read by agents at scale, used in training, summarized into derivatives, resold inside larger products. You need three things: terms enforcement at the page level, attribution that follows the data through agent pipelines, and the ability to revoke and have the revocation cascade through everything derived from the original.

What ships

Three primitives, one chain.

The full surface is open. Module paths shown.

Signed governance at the source. aps.txt for site-wide terms, embedded HTML blocks for per-page overrides, HTTP headers for header-only deployments. All Ed25519-signed and content-hashed.

generateGovernanceBlock
parseGovernanceBlock · verifyGovernanceBlock

Attribution that follows the data. Source receipts, access receipts, derivation receipts, decision lineage receipts. The chain from agent read to agent recommendation is reconstructable from signed primitives.

DataSourceRegistration → AccessReceipt
→ DerivationReceipt → DecisionLineageReceipt

Cascade revocation as enforcement. Revoke at the source and downstream derivatives invalidate. The revocation is signed, propagating, and replayable. Agents that ignore it are visible in the receipt ledger.

Attribution Primitive (D/P/G/C)
AMCS spec · six requirements, two layers

Architecture

The chain, end to end.

Each receipt is signed, content-hashed, and verifiable without the platform that issued it.

# 1. Source. You publish terms once.
POST /aps.txt  # Ed25519-signed governance block
# 2. Access. Agent fetches under its passport.
GET  /article/123  # issues AccessReceipt(agent_did, scope, ts)
# 3. Derivation. Agent transforms or summarizes.
EMIT DerivationReceipt(parent: AccessReceipt, weights: D/P/G/C)
# 4. Decision. Recommendation cites the source.
EMIT DecisionLineageReceipt(sources: [DerivationReceipt, ...])
# 5. Revoke. Cascade invalidates downstream.
REVOKE source_id  # every receipt that anchors back is now invalid

Proof

Verifiable on the public record.

●
AMCS spec live.
Cryptographic news provenance, six requirements across two layers, on aeoess.com/amcs.html.
●
VeritasActa cross-layer integrity 10 of 10.
APS DecisionLineageReceipt slots into external_receipts.aps. Verify PR #7.
●
Vocabulary registry covers data lifecycle.
Source, access, derivation, content provenance with multiple cross-vendor implementations.
●
Attribution Primitive specified.
Four-axis Merkle envelope (D/P/G/C), Build-B fractional weights, Build-C settlement records.

Adjacent