[services/shared] Define crypto package integration boundary

[FlowmemoryAI]

Objective

Define how services should consume the runnable FlowMemory crypto package without duplicating or drifting from v0 hash formats.

Allowed folders

• services/shared/
• services/verifier/
• crypto/
• docs/ARCHITECTURE.md only for short cross-links if needed

Forbidden folders

• contracts/RootfieldRegistry.sol
• apps/
• hardware/
• deployment scripts
• tokenomics
• production L1/appchain implementation
• zk proof implementation

Acceptance criteria

• A services/shared import or mirror strategy is documented.
• Service-side code can consume crypto/src/index.js or a deliberately mirrored package boundary.
• Compatibility tests use crypto/fixtures/ and crypto/test-vectors/.
• No network, RPC, database, deployment, or secret dependency is introduced.

Risk level

Medium

Recommended agent

Services Verifier Agent with Crypto Agent review.