[contracts] Define WorkerRegistry and VerifierRegistry authorization policy

[FlowmemoryAI]

Objective

Define the policy for WorkerRegistry and VerifierRegistry beyond the Live V0 self-registration skeletons.

Context

Live V0 includes minimal self-registration contracts with metadata commitments. They do not authorize protocol work, prove correctness, add staking, add rewards, or implement slashing.

Allowed folders

• contracts/
• tests/
• docs/DECISIONS/
• docs/SECURITY_MODEL.md

Forbidden folders

• apps/
• services/
• hardware/
• research/
• crypto/ except references
• Tokenomics, staking, slashing, dynamic fees, production hook deployment, production network config, or L1/appchain implementation

Acceptance Criteria

• Decide whether worker/verifier registration remains self-serve, allowlisted, attested, or governance-controlled.
• Document what registration does and does not authorize.
• If contract behavior changes, add focused tests.

Risk Level

Medium

Recommended Agent

FlowMemory Contracts Agent after verifier identity vocabulary stabilizes.