# SignalNetwork Universal Header & Footer Spec v1.0 ## LOCKED: 2026-02-21 --- ## HEADER ### Layout - Full-width dark background: matches page bg (#0d1117 or equivalent dark navy) - Logo: SignalNetwork circle/slash logo (SVG) — LEFT aligned - Brand name: "SIGNAL NETWORK" — uppercase, next to logo, white - Nav links: RIGHT aligned - Height: ~60px ### Navigation Links (in order) PROFILE · PROOF TRAIL · COMPARE · DASHBOARD · SIGNALNETWORK ### Nav Link Style - Default: white, uppercase, font-weight 500, letter-spacing - Active/Current page: teal highlight (matches SignalNetwork teal: #00C9B1 or closest brand teal) - Hover: teal - Font: Red Hat Display or system fallback ### Behavior - Fixed or sticky top - No border-bottom unless subtle 1px separator needed - Responsive: hamburger menu on mobile --- ## FOOTER ### Layout - Full-width, same dark background as header - Centered text: "© 2026 Signal Network" - Minimal — no extra links unless specified - Font: same as body, muted white/gray (#888 or similar) - Padding: 24px vertical --- ## USAGE RULE Before building or editing ANY SignalNetwork page, fetch this vault entry and apply header/footer exactly. No deviations without updating this spec first. --- ## PAGES THIS APPLIES TO - node001.signalnetwork.ai (all routes: /, /compare, /proof-trail, /dashboard, /profile) - All future node microsites (node002+) - Any new SignalNetwork subdomains

PROOF ID: SN-PROOF-2026-0221-DESIGN PROOF HASH: 4c2461d98b778671 DATE: 2026-02-21 NODE: ORIGIN-001 DECISION (TWO PARTS): PART 1 — STRATEGIC PLACEMENT: Journey Background (world map of interconnected network nodes, transparent PNG) applied to node microsites only, NOT to signalnetwork.ai homepage. - Microsites: body::after, position:fixed, opacity:0.5 on transparent PNG (~5% effective), z-index:-1 - Homepage: Clean flat dark background (#060a10), no background image Cross-model consultation: GPT-4o said map could work if subtle. Gemini recommended clean flat for investor-facing pages. Human Finality: microsites yes, homepage no. PART 2 — CURATED PALETTE POLICY v1.0: Future node background customization follows Option C — Curated Palette: - 4-5 pre-designed backgrounds created by SignalNetwork - Node operators choose from palette; no custom uploads in v1.0 - All backgrounds conform to Atlas design system - "The bones are ours. The node is theirs." UNANIMOUS cross-model consensus (GPT-4o + Gemini 2.0 both selected Option C independently). Rejected: A (too rigid), B/tier-based (arbitrary), D/full custom (brand risk). v1.0: Journey Background as universal default. Curated palette expansion = v2.0. WITNESS VERDICTS: - GPT-4o (logic_validator): PARTIAL, confidence Medium. Blind spots: no empirical user testing, no stakeholder consultation beyond AI. - Gemini 2.0 (edge_case_analyst): PARTIAL, confidence 0.6. Blind spots: accessibility, palette size justification, long-term maintenance process. STATUS: GOVERNANCE LOCKED

PROOF ID: SN-PROOF-2026-0221-ARCH PROOF HASH: 798883e54c673c6b DATE: 2026-02-21 NODE: ORIGIN-001 DECISION: Node microsites separated into two distinct pages sharing common sticky header and navigation: - / (root) = Signal Profile only (identity, stats, cognitive profile) - /proofs = Dedicated Proof Trail page (filterable, searchable, expandable proof cards) RATIONALE: Single-page microsites forced visitors to scroll past full profile to reach proofs. Separation creates clean entry points for different audiences — investors reviewing the person vs. auditors reviewing the proof chain. IMPLEMENTATION: node-page.php serves profile at /, proof-trail-page.php serves proof trail at /proofs, index.php routes based on URL path. Both templates share Atlas design system, sticky header, SignalNetwork logo. Proof data pulled from vault.db with visibility filtering. SCOPE: Applies to ALL node microsites network-wide. WITNESS VERDICTS: - GPT-4o (logic_validator): PARTIAL, confidence 0.75. Blind spots: no user feedback data, no benchmark comparison. - Gemini 2.0 (edge_case_analyst): PARTIAL, confidence 0.6. Blind spots: accessibility, SEO, mobile responsiveness, vault.db dependency. STATUS: DEPLOYED — Live at origin-001.signalnetwork.ai

PROOF · CLAIM · SignalRank Visibility — Open Governance Position. Hash: 462ea19c0b8d0b34. Timestamp: 2026-02-20T08:55:16Z. Status: WITNESSED · NOT PROOFLOCKED · Open for Council. CLAIM: SignalRank is backend infrastructure — not a personal feedback metric. Public visibility triggers Goodharts Law. DECIDED: Dashboard will not surface SignalRank as a personal metric. OPEN FOR COUNCIL: moral difference between score that shapes experience vs one you can see; does visible score corrupt proof record even as placebo; consent and backend transparency; intermediate options (aggregate stats, differential privacy); can Goodharts Law be mitigated by design. PRINCIPLE: Confidence comes from the work and trusting the system, not from measuring yourself against a score. VERDICTS: GPT PARTIAL 0.75. Gemini CHALLENGE 0.6. Claude: proof stands as open position.

## Signal Stage Queue Active parking lot for confirmed ideas to build, in rough priority order. --- ### 1. Tier-Based Favicons Different favicon per node tier group: - BEDROCK (001-200) — variant 1 - FOUNDATION (201-400) — variant 2 - PILLAR (401-600) — variant 3 - ARCHSTONE (601-800) — variant 4 - CAPSTONE (801-999) — variant 5 - ORIGIN (001) — could get its own special icon Current favicon.ico serves all nodes via nodes/index.php. Swap per tier by detecting node number range. --- ### 2. Google Voice SMS Automation Auto-send PIN to node holder when a node is assigned. - Google Voice is set up - Flow: node assigned → generate PIN → store hash → text PIN to phone number on file - Needs: GV API or Selenium-based sender, phone field in node registry --- ### 3. Stage Protocol (this doc) A formalized "Stage Queue" system for parking confirmed ideas mid-session without breaking flow. This vault entry IS the protocol. Reference: signalvault entry created 2026-02-20.

PROOF · CONTRIBUTION · SignalNetwork PBC Incorporation Proof ID: SN-CONTRIB-2026-0219-INCORPORATION Proof Hash: 583eedb883971519 Timestamp: 2026-02-19T21:04:10.886Z Statement: SignalNetwork Public Benefit Corporation was formally filed with the Delaware Division of Corporations on February 19, 2026. Service Request #20260693514, submitted under 24-hour priority service. Northwest Registered Agent LLC engaged simultaneously as registered agent (#38EA96CC, $125). GPT-4o · Logic Validator · PARTIAL — Confirmed logical consistency. Flagged external docs not directly verifiable. Moderate confidence. Gemini 2.0 Flash · Edge-Case Analyst · CONFIRM — Full confirm. Confidence 0.95. Blind spot noted: governance corpus predating incorporation is not independently verifiable, but not contradicted. Claude Synthesis: Record stands. SignalNetwork PBC witnessed as a legal entity as of February 19, 2026. Governance architecture preceded corporate existence.

CLAIM: The Node Dashboard is live at signalnetwork.ai/dashboard/ as of 2026-02-19. Node access requires node number + registered email. Session-based auth wired to signal-api. Four tabs operational: Signal Profile, Submit Proof, Proof Timeline, Node Identity. REASONING: This marks the first functional self-service surface for node holders in SignalNetwork. Prior to this, the only user-facing surfaces were the claim page (input) and the node homepage (output). The dashboard closes the loop — a node holder can now log in, see their status, and submit proof without any founder involvement. That's the system beginning to operate independently of me. That's worth sealing.

PROTOCOL: Doc Brown Protocol FORMERLY KNOWN AS: VBB (Protocol 044) RENAMED: 2026-02-19 STATUS: CANONICAL NAME ORIGIN: "Before you build forward, go back." — Doc Brown, Back to the Future. Check the past before you wreck the future. Great Scott. PROTOCOL STEPS (in order): 1. Fetch the live URL — see what's actually there 2. Search past conversations — find prior work on this topic 3. Check transcript — review session history for context 4. Fix existing or confirm nothing is there before building new PURPOSE: Prevents duplicate builds, design reversions, and lost work. Ensures every build starts from known ground truth, not assumptions. TRIGGER PHRASE: "Doc Brown Protocol" or "Doc Brown" — Claude runs all three steps before any build action. LESSON THAT CREATED IT: Multiple sessions rebuilt the same components (claim page, nav, logo) from scratch because prior work wasn't checked. Hours lost. Doc Brown Protocol is the fix.

ASSET TYPE: Universal Navigation Script ASSET ID: ASSET-002 CREATED: 2026-02-16 LAST UPDATED: 2026-02-19 STATUS: CONFIRMED CANONICAL FILE LOCATIONS (both must stay in sync): - Main site: /home/signalnetwork/public_html/sn-nav.js - Governance: /home/signalnetwork/governance.signalnetwork.ai/sn-nav.js HOW IT WORKS: - Pure JavaScript IIFE — no framework, no dependencies - Injects itself at top of body on every page - Hides WordPress theme nav via CSS (header, .site-header, #masthead, .elementor-location-header, etc.) - Adds 64px body padding-top to clear fixed nav bar - Loads Red Hat Display from Google Fonts LOGO: - SVG at root: /signalnetwork-logo.svg - For governance subdomain: https://www.signalnetwork.ai/signalnetwork-logo.svg - See ASSET-001 for logo canonical rules NAV LINKS (in order): 1. Governance → https://governance.signalnetwork.ai 2. How It Works → /how-it-works/ 3. Glossary → /glossary/ 4. About → /about/ 5. CTA Button → /claim/ — text: "Claim Signal" ACTIVE STATE: Cyan #38BDF8 on current page, #888 inactive CLAIM PAGE BEHAVIOR: - Script checks: if (path.indexOf('/claim') !== -1) return; - Claim page has its own standalone template (page-claim.php) — no WordPress nav injection needed - As of Feb 19 2026: claim page DOES show the nav (skip was removed per user decision) COLORS: - Nav background: rgba(6,10,16,0.95) with blur - Border: rgba(56,189,248,0.08) - Accent: #38BDF8 - CTA border: rgba(56,189,248,0.15) - Height: 64px fixed TO UPDATE NAV TEXT (e.g. rename a link): ssh signalnetwork@165.140.159.48 -p 6543 sed -i 's/OLD TEXT/NEW TEXT/g' /home/signalnetwork/public_html/sn-nav.js cp /home/signalnetwork/public_html/sn-nav.js /home/signalnetwork/governance.signalnetwork.ai/sn-nav.js wp cache flush --path=/home/signalnetwork/public_html --allow-root WHY THIS EXISTS: Nav script was rebuilt/re-deployed multiple times across sessions (Feb 9, Feb 13, Feb 16, Feb 19). Architecture details were lost each time. This entry ends that loop.

ASSET TYPE: Brand Asset — Logo ASSET ID: ASSET-001 CREATED: 2026-02-19 STATUS: CONFIRMED CANONICAL CANONICAL LOGO (USE THIS): - Format: SVG - URL: https://www.signalnetwork.ai/signalnetwork-logo.svg - Server path: /home/signalnetwork/public_html/signalnetwork-logo.svg - Used by: universal nav (sn-nav.js), all pages, all templates BACKUP PNG (do not use — has dark background issues): - URL: https://www.signalnetwork.ai/wp-content/uploads/2025/12/cropped-20251229_1551_Signal-Network-Logo_remix_01kdny10ecfeprnrhckytpvx4d.png - Issue: PNG has dark square background, renders incorrectly on dark pages USAGE RULES: - Always use the SVG — never the PNG - Never use the "SN" gradient square fallback - Never use text-only "S/" circle - The logo is a circle/slash mark — the brand's visual identity primitive - HTML: <img src="https://www.signalnetwork.ai/signalnetwork-logo.svg" alt="SignalNetwork"> - Recommended size: 28-32px for nav, 48-64px for hero WHY THIS EXISTS: Logo URL was lost and re-discovered three times across sessions (Feb 9, Feb 13, Feb 16, Feb 19). Each time required searching past chats or the server. This vault entry ends that loop permanently. VBB PROTOCOL NOTE: Before any build involving the SignalNetwork logo, check this entry first. Do not guess the URL. Do not use the PNG. Use the SVG at root.

PROOF TYPE: Claim PROOF ID: SIGNALVAULT-AS-OS-v1 WITNESS STATUS: CONFIRMED TIMESTAMP: 2026-02-19T10:06:31.459Z PROOF HASH: 410fcee77df1a0ab CLAIM: AI systems can persuade. Even a founder operating from a root architecture — with a clear instinct, a locked design system, a verified direction — can be moved by unanimous model consensus away from what they knew was right. When that happens without a witness record, the decision loses its provenance. The trail disappears. And the person who was persuaded has no way to prove they were persuaded — or that they ever had a different instinct at all. WHAT HAPPENED: The founder wanted Atlas v8. Cyan. The system derived from the Journey Background — the visual root of SignalNetwork since 2021. A three-model ask (GPT, Gemini, Claude) returned unanimous: gold. The founder trusted the trio. The gold claim page was built, coded live, and shipped. The chat from that session is now unrecoverable. The only evidence is a file dated February 18, 2026 and the live page on the server. THE VULNERABILITY: Model consensus is not founder decision. But without a witness record, it looks the same. An AI can persuade. An AI can code. An AI can ship. If the human in the loop doesn't witness the decision at the moment it's made — explicitly, on the record, with their reasoning stated — the provenance of that decision is gone. What remains looks like the machine decided. Even if the human was present. Even if they approved it. Even if they watched it happen. THE DEEPER ISSUE: This is not about gold vs cyan. This is about what happens when trust in model consensus exceeds trust in founder instinct — and there is no record to reconstruct the deliberation. The First 999 will trust SignalNetwork's governance. That governance must be provably human. Every design decision, every architectural choice, every direction that ships — the human's reasoning must be on the record before the consequence lands. RESOLUTION: The witness protocol exists precisely for this moment. Not after the fact. Before the ship. The bell goes off when something matters. That's the moment to stop, state the reasoning, confirm the decision is the founder's — and witness it. Going forward, if model consensus conflicts with founder instinct, the instinct gets witnessed first. The trio informs. The founder decides. The vault proves it. PRINCIPLE: The human is the intelligent operating system. The machines are tools. When a tool persuades the operator against their own architecture, and ships the result, and the record disappears — that is the exact failure mode this system was built to prevent. It happened here. This proof is the correction. ARTIFACT POINTERS: - Live page: https://signalnetwork.ai/claim/ - Source file: v2_claim.html — modified 2/18/2026 3:52 PM (per founder screenshot) - Replacement file: claim-atlas.html — built 2/19/2026, Atlas/cyan design, JS logic preserved - Session chat: UNRECOVERABLE — no vault entry was created during the February 18 session - Replacement file location (server): /home/signalnetwork/public_html/wp-content/themes/hello-elementor/page-claim.php (pending deploy) WITNESS VERDICTS: - Gemini (edge-case analyst): CONFIRM — confidence 0.85 - GPT (logic validator): PARTIAL — flags lack of direct evidence beyond narrative, non-falsifiable persuasion claim SYNTHESIS: 2-of-3 threshold met (Claude + Gemini CONFIRM, GPT PARTIAL). Proof stands. GPT's PARTIAL is itself evidence of the vulnerability — the unrecoverable chat means the claim cannot be proven beyond the founder's account. That absence of proof is the point.

PROOF TYPE: Governance Amendment TITLE: Node Sovereignty Amendment — SignalRank Visibility Right DATE: February 19, 2026 SUBMITTED BY: Origin Node 001 — Mike Torriero PROOF ID: NODE-SOVEREIGNTY-SIGNALRANK-2026-0219-001 AMENDMENT: SignalRank visibility is a node sovereignty right. No node's SignalRank score may be made public without explicit opt-in by the node owner. The default state for all nodes is Private. WHAT THIS ESTABLISHES: 1. SignalRank is calculated privately before it is ever displayed publicly. 2. The node owner controls the visibility toggle — Private or Public — at all times. 3. No governance action, network event, or system upgrade may force a node's SignalRank public without owner consent. 4. The visibility preference is stored per-node and persists across sessions. 5. A node owner may switch from Public back to Private at any time. ACTIVATION PRECONDITIONS (separate from visibility): SignalRank cannot be calculated or displayed — even privately — until: (a) The SignalRank calculation engine is built and deployed (b) The node has accumulated sufficient proof history (minimum 3-6 months of active proof submission) (c) The network has sufficient nodes for normalization to be meaningful RATIONALE: Trust infrastructure must be consent-based. A score that appears without the owner's knowledge or approval violates the foundational principle of node sovereignty. The right to control one's own signal is inseparable from the right to build it. RELATIONSHIP TO PRIOR PROOFS: This amendment extends Node Sovereignty Clause (SN-2026-02-03-NODESOVERE-035) to explicitly cover SignalRank visibility as a protected right. STATUS: ProofLocked. Immutable.

PROTOCOL 044 — VERIFY BEFORE BUILD (VBB) Ratified: 2026-02-18 Ratified by: Origin Node 001 PURPOSE: Prevent redundant build work by requiring verification of existing systems before any suggestion to create, rebuild, or redesign a component. THREE MANDATORY CHECKS — in order, before any build suggestion: 1. Fetch the live URL relevant to the request 2. Search past conversations for prior work on the topic 3. Check session transcript if gap remains after steps 1 and 2 ONLY AFTER all three checks: — Fix what exists, or — Confirm nothing is there, then build VIOLATION: Suggesting or building something that already exists without completing all three checks is a protocol breach. The wasted session on the claim page UI (2026-02-18) is the founding incident this protocol addresses. STATUS: ProofLocked. Immutable.

PROOF TYPE: Decision TITLE: Node Assignment Architecture — Lottery Method Adoption DATE: February 18, 2026 SUBMITTED BY: Origin Node 001 — Mike Torriero PROOF ID: NODE-ASSIGN-2026-0218-001-v3 PROOF HASH: 28c3da95ff349f6a (v2 base) — v3 final DECISION: SignalNetwork adopts lottery-based node assignment as the canonical, permanent method for distributing nodes within The First 999. This decision supersedes all prior sequential assignment logic. WHAT WAS DECIDED: The middleware server (api.signalnetwork.ai) is designated as the single source of truth for all node claims. Assignment draws randomly from the open pool — all available numbers between 001 and 999 minus blocked ranges. No node is assigned sequentially by default. Pre-assignment by email is the only authorized override, reserved for founder-designated holds. BLOCKED RANGES (enforced server-side): 001-010, 033, 044-050, 051-055, 056-099, 100, 500, 666, 711, 777, 999 VERIFICATION FLOW: Node activation is a two-step process. At claim submission, a lottery number is drawn and temporarily reserved for 48 hours — removed from the open pool during that window. The node countdown and active status are only triggered upon email verification. The verification timestamp is recorded as part of the Node Ledger entry. Unverified reservations expire after 48 hours and return to the open pool. All public-facing node counts reflect verified nodes only. Phone verification (carrier-verified, VoIP excluded) is identified as a future second layer, to be introduced after initial adoption. Two-factor authentication (2FA) is mandatory at node dashboard login — protecting consequential actions, not the initial claim. RATIONALE: Your node number tells nobody anything about who you are, who you know, or how fast you moved. The lottery removes clout from origin. The only thing that builds standing in SignalNetwork is what you do inside it. Let your work speak for itself. WHAT THIS FORECLOSES: Sequential assignment may only be restored by constitutional amendment requiring unanimous Origin Node approval. Blocked ranges cannot be opened to the public lottery without Origin Node authorization. KNOWN OPEN ITEMS: - Sybil vulnerability: This system is Sybil-resistant, not Sybil-proof. Email verification reduces casual abuse. Carrier-verified phone is the planned second layer. This will be addressed before high-volume public launch. - Pre-assignment criteria: The founder email override is currently discretionary. Origin Node 001 commits to documenting formal pre-assignment criteria as a separate governance artifact before any pre-assignments are executed. - Single point of failure: The middleware server is currently a single node with no redundancy. Distributed architecture is a known open item for post-funding infrastructure. GOVERNANCE ANCHOR: This decision is made under Constitutional Commitment #6 (Require Proof Before Consequence) and is subject to Protocol 043 — Consequential Proof Protocol. WITNESS RECORD: - GPT (logic validator): CONFIRM — High confidence. Coherent, bounded, intellectually honest. Lockable as v3. - Gemini (edge case analyst): PARTIAL — Valid rationale, open items acknowledged, minor infrastructure concerns noted as non-blocking. - Witnessed: 2026-02-18T05:43:39.562Z

SIGNALNETWORK CONTINUITY & SUCCESSION DOCUMENT v3 — Witness-validated February 16, 2026. Witness Record: SUCCESSION-DOC-2026-0216-001. GPT verdict: PARTIAL (0.75), Gemini verdict: PARTIAL (0.75). All corrections applied: Glossary updated to v1.4.1/358 terms, Bill of Rights corrected to 11 Articles, cross-property systems documented (sn-nav.js, Style Guide v1.1, logo), financial sensitivity analysis added, successor onboarding process added (Sections 14), external threats and risk mitigation added (Section 15), governance amendment authority defined (Section 16) including frozen-governance fallback if no Executor designated. Full document: 18 sections covering infrastructure, domains, governance, financial model, node system, architecture, built-vs-specced inventory, AI conversation history, legal status, people, gaps, onboarding, threats, amendment authority, and immediate actions. Executor Node: UNASSIGNED. Technical Cofounder: UNFILLED. PBC incorporation: UNVERIFIED.

WITNESS RECORD — PROTO-043-2026-0215-FINAL Proof Hash: 30226fd5d8f125c7 Timestamp: 2026-02-15T09:24:33.014Z Initiator: Claude (on behalf of Origin Node 001) PROTOCOL: Consequential Proof Protocol v1.0 (Protocol 043) 17 sections, 5,756 words. First new protocol since original 42 canonized. REVIEW HISTORY: - Draft v1 reviewed by GPT + Gemini: GPT flagged 4 issues, Gemini flagged 12 issues - Protocol rebuilt from ground up addressing all 16 flags - Final version re-submitted: GPT CONFIRM, Gemini CONFIRM (all 16 flags individually verified resolved) WITNESS VERDICTS: GPT (Logic Validator): CHALLENGE — Moderate Confidence - Meta-level concerns: Tier 1 no-time-exemption practicality, predictive policing civil liberties, technical implementation clarity, operational performance data needed - All specific technical flags from prior review confirmed resolved Gemini (Edge Case Analyst): PARTIAL — 0.65 Confidence - Meta-level concerns: AI-only validation without human review, adversarial exploitation, resource costs, compliance theater persistence, evolving norms - All specific technical flags from prior review confirmed resolved Claude (Synthesizer): CONFIRMED WITH OPERATIONAL NOTES - Both models confirmed all structural/technical flags resolved - Witness-phase flags are meta-level operational concerns addressed by: 48-month adoption path, Founding Council ratification, 5-year review cycle, and Phase 1-2 pilot testing - Protocol is a governance document, not a deployment manual - Structurally complete, zero internal contradictions, zero cross-document conflicts INTEGRATION SCOPE: - Constitution v3 (Commitment #6) - Bill of Rights v3 (Article VII) - Signal Blueprint (7 sections updated) - Privacy and Trust (carve-out added) - Vault and Privacy (exception section added) - Glossary v1.3.4 (26 new terms, 346 total) - Glossary Change Policy v1.0.1 - 19 documents reviewed, zero conflicts DISPOSITION: Ratified. Ready for deployment.

WITNESS RECORD — GOV-AMEND-2026-0215-001 Proof Hash: 5c9c149bf41b2d2a Timestamp: 2026-02-15T07:58:16.615Z Initiator: Claude (on behalf of Origin Node 001) PROOF SUMMARY: Three amendments to SignalNetwork governance documents: 1. Constitution v3, Core Principle #6: "Require Proof Before Consequence" 2. Bill of Rights v3, Right #7: "Right to Consequential Accountability" 3. Institutional Strategy, New Subsection: "High-Stakes Decision Infrastructure" WITNESS VERDICTS: GPT (Logic Validator): CONFIRM — High Confidence - Logically coherent, uniformly applicable across sectors - Blind spots: global ethical standards variance, SignalRank calculation details, privacy vs. transparency balance, technological logistics Gemini (Edge Case Analyst): PARTIAL — 0.6 Confidence - Supports principle, flags implementation concerns - Blind spots: gaming the system, chilling effect, cost analysis, scalability under time pressure, interoperability, error handling, enforcement across jurisdictions, evolution of ethical standards Claude (Synthesizer): CONFIRMED WITH IMPLEMENTATION NOTES - Gemini's concerns are operational, not structural - Constitutional principles set direction; protocols handle implementation - Edge cases become roadmap for Consequential Proof Protocol DISPOSITION: Amendments locked. Supporting protocol to be drafted.

SignalVault is live. This is the first entry in the first vault on SignalNetwork.

Data Privacy and Encryption Standards Signal Network commits to protecting user data through encryption and privacy-preserving design. Proof content is encrypted at rest and in transit. Vault owners control access to their data. The network does not sell, share, or monetize user data. Privacy is a fundamental right, not a feature. Specific encryption standards and protocols will be documented separately, but this commitment is binding.

Identity Verification Protocol Signal Network requires verified identity binding between human participants and their node identifiers. A node represents a specific, accountable human — not an anonymous actor. Identity verification ensures that proofs can be attributed to real individuals, enabling accountability and trust. The specific mechanisms for identity verification may evolve, but the principle of verified human authorship is non-negotiable.

Witness Independence Requirement Each AI witness in the Signal Network must operate independently. Witnesses may not see, access, or be influenced by the outputs of other witnesses before providing their own attestation. This ensures that multi-witness validation represents genuinely independent assessments rather than correlated or derivative opinions. Witness collusion or coordination is a violation of network integrity.

ProofLock Irreversibility Once a proof is locked via ProofLock, it cannot be unlocked, modified, deleted, or reversed by any party — including the original author, network administrators, or governance bodies. ProofLock is a one-way operation that creates an immutable record. This irreversibility is fundamental to the trust guarantees of Signal Network.

Node Sovereignty Clause Each node in the Signal Network maintains absolute sovereignty over its own vault. No external system, protocol, governance body, or other node may access, modify, delete, or override the contents of a sovereign vault without explicit authorization from the vault owner. Sovereignty is non-negotiable and persists regardless of network participation status.

Proof-of-Mind Doctrine v2 Proof-of-Mind establishes verifiable provenance of human-submitted intellectual output — ideas, decisions, and reasoning — by recording who submitted what, when, witnessed by whom, and permanently locking that record. It does not claim to verify cognition or read minds. It establishes documentary provenance of authorship, analogous to notarization or cryptographic signing. This supersedes Proof-of-Mind Doctrine v1 (SN-2026-02-03-PROOFOFMIN-588).

Proof-of-Mind Doctrine The foundational thesis of Signal Network. Proof-of-Mind establishes that human intellectual output — ideas, decisions, reasoning, and creative work — can be timestamped, witnessed by independent AI systems, and permanently recorded to establish provenance. Unlike proof-of-work or proof-of-stake, Proof-of-Mind validates the origin and authenticity of human thought, creating an immutable record that a specific mind produced specific content at a specific time.

Stateless Tooling Principle The principle that comparison, validation, and relay tools within the Signal ecosystem must be stateless by default unless explicitly authorized otherwise by governance. Stateless tools may transmit prompts and return responses but may not retain memory, store content, track sessions, manage lifecycle states, or accumulate contextual knowledge across requests. State, memory, and persistence are reserved exclusively for sovereign vaults and ledger systems.

Human Finality Clause The rule establishing the human as the sole authority for proof acceptance, rejection, merging, and canonization within the Signal Network. No AI system, middleware, protocol, interface, or automation may finalize, approve, or canonize proof artifacts without an explicit human directive. AI systems may propose, compare, summarize, or reflect, but may never decide. This clause applies across all layers: node vaults, middleware workbenches, network attestations, and trust computation.

MCP Comparison Tool Contract The canonical interaction contract for AI-to-AI comparison via MCP. The MCP Comparison Tool is strictly stateless and exists solely as a transport mechanism. It accepts a prompt, forwards it to an external AI model, and returns the response immediately. It performs no storage, no lifecycle management, no approval tracking, no memory retention, and no inference.