docs: clarify context vs human-governance boundary in local-hybrid slice

[mdheller]

Summary

Add a short boundary note to the local-hybrid slice area clarifying that governed context and human-governance are distinct semantic planes.

Why

The slice pack is now merged on main, and we want the transport-facing documentation to preserve one important architectural split:

• slash-topics owns topic-pack identity / locality / provenance / movement semantics
• human-digital-twin owns policy / consent / approval / attestation semantics
• TriTRPC may carry frames from both planes without redefining their ownership

File added

• spec/slices/local_hybrid_v0/context_vs_human_governance_boundary.md

Review focus

1. Is the separation clear enough for future method/fixture work?
2. Should this later be folded into the slice README once convenient?
3. Does this reduce the risk of transport docs collapsing adjacent semantic layers into one metadata bucket?

[mdheller]

@copilot fix failed checks

[Copilot]

Pull request overview

Adds a short documentation note to the local-hybrid slice pack clarifying that “governed context” and “human-governance” are separate semantic planes owned by different upstream repositories, and that TriTRPC should not collapse or redefine that ownership when transporting frames.

Changes:

• Add a boundary note describing the governed-context vs human-governance split and upstream ownership.
• Clarify the implication for TriTRPC transport fixtures/docs (it can carry both, but doesn’t own their semantics).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[mdheller]

@copilot Fix failed checks

[mdheller]

@copilot fix the failed checks

[mdheller]

@copilot dix failed checks

[Copilot]

@copilot dix failed checks

Fixed in 103a820. The CI had multiple cascading failures:

1. AEAD algorithm mismatch: All fixture tags use BLAKE2b-MAC (hashlib.blake2b, key=0x00*32, digest_size=16), but the Rust tests, Go tests, and Python verifier were checking with XChaCha20-Poly1305. Updated all three.

2. Mode roundtrip failure (revealed once Add pedantic repository documentation (THEORY.md, REPOSITORY_GUIDE.md) and expand README #1 was fixed): BuildEnvelope/build always wrote mode=0, but PathB fixtures use mode=1. Added BuildEnvelopeWithMode/build_with_mode functions that preserve the decoded mode bytes.

3. Go TLEB3 tail-marker bug (the root cause of the initial Go test panic): TLEB3DecodeLen processed tail-marker bytes (0xF3–0xF6) one byte at a time, but they span 2 bytes. Fixed to read both bytes together, matching the existing Rust implementation.

make verify now passes all steps: rust-fmt, go-fmt, rust-test, go-test, fixtures.

@copilot Fix failed checks

Fixed in commit 103a820. See the detailed breakdown in the reply above.

@copilot fix the failed checks

Fixed in commit 103a820. See the detailed breakdown in the reply above.