SIGNAL.ZERO Doctrine + Whitepaper (Plaintext)
https://www.signalzero.ink/doctrine

Doctrine (Overview)
SIGNAL.ZERO is Proof of Continuity Infrastructure (PoCI).
It produces a Commitment Object: Genesis (activation) + continuity history (signals over time).

Vision
Make maintained intent legible and composable across products as a standard primitive.

Mission
Ship and maintain the canonical PoCI reference implementation:
Genesis for activation, one signal per day, and stable read APIs for real products.

Whitepaper (System specification)
- Category: Proof of Continuity Infrastructure (PoCI)
- Output is designed to be read by other systems.
- Requirements: time-based, low-noise, verifiable, composable.

Problem definition
Web3 is strong at proving ownership/transactions but weak at proving maintained intent.
Without PoCI, products fall back to token gating, paywalls, social graphs, or unverifiable off-chain reputation.

Use cases
- Membership eligibility based on Genesis + windowed continuity thresholds.
- Contributor/program screening based on sustained presence.
- Governance weighting based on continuity rather than token balance alone.
- Sybil friction without KYC: time becomes a cost.

Architecture
- Genesis: ERC-721 activation credential; one per wallet; required to submit signals.
- Signals: one wallet-signed check-in per 24h window; records presence (no content).
- Read surfaces: stable endpoints for status, history, and cohort evaluation.

Chain strategy
- Live today: Base Sepolia (84532) for thorough testing.
- Production target: Base mainnet (8453) after auditing.

Not in the UI
No feeds, no gamification, no financial incentives tied to signaling, and no social graphs.

Canonical links
- PoCI spec: https://www.signalzero.ink/poci (plaintext: https://www.signalzero.ink/poci.txt)
- Developer docs: https://www.signalzero.ink/doc (plaintext: https://www.signalzero.ink/doc.txt)