[thystra]

Activity-Relay 3.0 FEP-ae0c foundation handoff

Generated: 20260801T200743Z

Exact provenance

• Stable baseline tag: v2.5.0
• Stable baseline commit: cbe77b5f44a9d6dc82dd2f8ab2e2c90a2021e8bb
• Design branch: design/v3-fep-ae0c-compatibility
• Runtime behavior changed: no
• Configuration changed: no
• Redis data changed: no

Public files changed

• AGENTS.md
• TODO.md
• docs/FEP-AE0C-COMPATIBILITY.md
• docs/INTEGRATION-TESTING.md
• docs/INTEROPERABILITY.md
• testdata/fep-ae0c/cases.json
• contrib/ops/test_fep_ae0c_cases.py

Design results

• Characterizes both FEP-ae0c relay families.
• Records current v2.5.0 behavior and Activity-Relay extensions.
• Identifies Public-in-to versus Public-only-in-cc as an explicit
  policy decision.
• Separates document-level Linked Data proofs from HTTP message signatures.
• Preserves open publishers, broad actor compatibility, NodeBB normalization,
  and authorized fetch as deliberate extensions.
• Requires a mixed two-relay duplicate/reflection audit.
• Defines an additive RFC 9421/RFC 9530 path for Activity-Relay 3.0.
• Records alternative durable-state backends as tabled.
• Retains stale-receiver cleanup as configurable, report-first future work with
  hard safety invariants.

Validation completed

• Exact v2.5.0 tag/master baseline verification
• Exact changed-path manifest
• JSON syntax and fixture-schema tests
• Documentation-content and private-data audit
• No runtime, configuration, workflow, or packaging changes
• Full serialized Redis-backed Go tests
• Full serialized Redis-backed race tests
• Go vet
• Static-site Python tests
• Operations Python tests

Backup

/home/alan/src/backups/activity-relay-backups/20260801T200743Z-before-v3-fep-ae0c-foundation-r3

Current state

The validated files are installed on design/v3-fep-ae0c-compatibility and remain uncommitted.
Nothing has been pushed, tagged, published, deployed, or changed in production.

Recommended next review

1. Review the compatibility matrix and every fixture disposition.
2. Decide whether the Public-only-in-cc policy remains open or receives a
   preferred 3.0 default.
3. Confirm that Linked Data proof generation remains outside the initial RFC
   9421 milestone.
4. Commit and push this design-only branch after review.
5. Begin a separate characterization-test branch before any runtime refactor.