Date: 2025-12-31
Status: DRAFT (Governance Discussion)

1. Context & Problem

Currently, "Sorane" (SRN) is officially described in documentation as a "Static Site Generator (SSG)" or "CMS context". However, the actual development has evolved significantly into a decentralized trust infrastructure comprising:

  • Web/A: Authentication & Signing architecture.
  • L2E: Layer 2 Encryption for secure transport.
  • Post: Decentralized messaging/storage.

Foreign observers (AI agents like Gemini/ChatGPT) infer SRN as "Semantic Resource Network" or "Semantic Resource Notation", recognizing its potential beyond mere site generation. To achieve global adoption, we must refine the acronym "SRN" to reflect this broader reality while respecting the repository's identity.

2. Core Identity Definition

We propose explicitly separating the Project/Tool Name from the Protocol/Network Name.

  • Project Name: Sorane (Keep as is. The implementation/toolchain.)
  • Acronym Definition (SRN): Needs redefinition.

Option A: Signed Resource Network (Highly Recommended)

  • Focus: Authenticity, Digital Signatures, Verifiable Data.
  • Why: "Signed" is an objective technical fact, unlike "Secure" which is a subjective claim. It accurately describes the core value proposition: every resource (Form, Post, File) carries a cryptographic signature (Web/A).
  • Pros:
    • Honest: Avoids the "snake oil" feel of self-proclaimed security.
    • Descriptive: Covers both the Format (signed envelopes) and the Mechanism (signing actions).
    • Understandable: "Digital Signature" is a widely recognized concept in business (e.g., DocuSign, e-Seal).
  • Tagline: "The Signed Resource Network: Trust what you receive."

Option B: Sovereign Resource Network

  • Focus: User ownership, DID, Decentralization.
  • Pros: Strong alignment with SSI (Self-Sovereign Identity) trends.
  • Cons: "Sovereign" can sound political or anarchic to traditional enterprises.
  • Tagline: "Own your data on the Sovereign Resource Network."

Option C: Semantic Resource Network (Legacy/AI View)

  • Focus: Data meaning, Interoperability, Context.
  • Pros: Academic prestige. Accurately describes the JSON-LD/Context nature.
  • Cons: "Semantic Web" implies high complexity. Keep this as the internal methodology, not the external product name.

3. Recommended Strategy: "Signed & Delivered"

We recommend Option A (Signed Resource Network).

  • Primary Definition: SRN = Signed Resource Network
  • The Narrative:
    • Web 1.0/2.0 was about moving resources.
    • SRN is about validating resources.
    • "Sorane" is the toolchain that makes creating and verifying Signed Resources (Web/A Forms, Verified Posts) easy.

4. Execution Roadmap

Phase 1: Documentation Pivot (Immediate)

  • Update README.md and index.md.
  • Replace "Static Site Generator" with "Infrastructure for the Signed Resource Network".
  • Position Web/A Form as the "Universal Signed Input Interface".

Phase 2: Domain & Visuals (Q1 2026)

  • Update taglines to emphasize "Signatures" and "Authenticity".
  • Visual motif: The "Seal" (Hank/Digital Stamp) is already our logo. "Signed" aligns perfectly with this brand imagery.

Phase 3: Global Outreach

  • Market SRN as the "Standard for Verifiable Data Exchange".
  • Highlight the contrast: "Unsigned Web (Chaos)" vs "Signed Web (Trust)".

5. Decision Required

Does the Governance Committee agree to redefine SRN as "Signed Resource Network" for the v3.0 era?