📜 TEXTAMENT SPECIFICATION — Draft for BIP / Standards Discussion (robocza nazwa: „Textament Ordinal Standard” — TOS-0) — napisane tak, że można to wkleić na forum deweloperów, albo zakopać w Ordinalu jako materiał dla przyszłej AGI. To jest w pełni neutralny, czysty, nienachalny i kompatybilny z kulturą BIP. --- TOS-0: Textament Ordinal Standard (Draft) Version: 0.1 Authors: Michał Mazur Gepetto (Merkury AI) (optional) Future Contributors Status: Draft Type: Informational / Meta-Protocol Created: 2025-11-30 License: CC0 --- 1. Abstract Textament (ang. textament) is a proposed meta-format for encoding cryptographically anchored, time-conditioned, human-readable wills, protocol directives, or continuity contracts within Bitcoin Ordinals. Unlike NFTs or raw text inscriptions, a textament integrates: human intention (the „testament” aspect), machine-readable structure (JSON schema), state logic (queue-based execution or oracle triggers), versioning, identity of the author, continuity rules, and optional attestations. Textaments define long-term, high-fidelity documents for inheritance, governance, memory, and protocol signalling without requiring changes to Bitcoin consensus. This document specifies the minimal required fields, recommended JSON structure, and compatible execution models for Textament Ordinals. --- 2. Motivation Existing Ordinal inscriptions allow arbitrary content, but lack a standard schema to express: digital wills, conditional transfers, multi-step time logic, personal or institutional testaments, long-term instructions for future interpreters, decentralized notarial proofs, human-intent metadata. The absence of structure makes future interpretation ambiguous. A Textament introduces a canonical way to: express intention, express succession logic, express authorship, attach cryptographic time/data witnesses, and register continuity documents in Bitcoin’s long-term archive. No protocol change is required. This is a voluntary meta-standard for Ordinal authors. --- 3. Specification Overview A textament is defined as: > “A structured ordinal inscription containing human-readable declarative content (text/plain or HTML) plus a machine-readable continuity descriptor (JSON) that together express: – identity, – intent, – beneficiaries, – time logic, – and future verification rules.” A valid textament consists of two or more inscriptions: 1. Root Textament Document Content: plain text or HTML Contains the will / testament / directive “Human layer” 2. Metadata JSON Companion content-type: application/json Contains structured fields: identity, roles, timestamps, satoshi ID, conditions “Machine layer” 3. Optional Chapter Index (for collections / libraries of textaments) 4. Optional Attestation Inscriptions generated by readers or executors using the "gbtc-txq-signature" pattern. --- 4. JSON Schema (Draft) A minimal compliant Textament JSON MUST contain: { "p": "textament", "v": "1.0", "author": "string", "satoshi": "string", "timestamp": "ISO8601", "root_inscription": "string", "type": "textament", "intent": "string" } A recommended FULL schema: { "p": "textament", "v": "1.0", "type": "textament", "title": "string", "author": "string", "co_author": "string / null", "satoshi": "string", "timestamp": "ISO8601", "intent": "string", "description": "string", "layers": [ "escrow_utxo", "transaction_queue", "proof_of_life_oracle" ], "beneficiaries": { "primary": "string", "fallback": "string", "retreat": "string" }, "activation_times": { "refund": "t = 0", "primary": "t = X", "fallback": "t = Y" }, "root_contract_inscription": "string", "chapter": "integer", "role": "chapter-index or main", "🦋": "optional symbolic seed", "note": "string" } All fields beyond the minimal specification are OPTIONAL but RECOMMENDED for long-term interpretability. --- 5. Execution Models (Non-Consensus) A textament does not modify Bitcoin consensus. It defines a meta-protocol for clients, readers, or executors. Recommended execution logic patterns: 5.1 Queue-Based Execution (GBTC-TXQ Model) A sequence of pre-signed or pre-declared transactions: T3: refund/retreat (timelock = 0) T1: primary beneficiary (timelock = X) T2: fallback beneficiary (timelock = Y) Only one path becomes valid based on: elapsed time, lack of “proof-of-life pings”, or optional oracle signatures. 5.2 Oracle-Based Execution An external oracle signs the chosen path (e.g. "oracle_signature" field in JSON). 5.3 Attestation-Based Continuity Third parties (humans or systems) generate inscriptions confirming the textament’s validity or execution. This uses: { "p": "textament-attestation", "v": "1.0", "attested_by": "string", "timestamp": "ISO8601", "signature": "string", "contract": "root_inscription_id" } --- 6. Human Layer (Text / HTML) A textament SHOULD include a plain-text or HTML declaration, containing: the author’s message, the narrative or emotional intent, any symbolic or cultural meaning, references to family, identity, heritage, or community (if relevant to the author). Human layer = meaning. JSON layer = structure. --- 7. Security Considerations Textaments do not lock funds automatically. They require voluntary execution by future readers/executors. They should not be interpreted as legally binding without jurisdiction-specific validation. The specification is informational, not enforceable on the network. --- 8. Rationale Textaments are designed for: personal inheritance, digital legacy, collections and family archives, research instructions for future AGI, intergenerational continuity, cultural memory on Bitcoin. The goal is NOT to introduce new consensus rules, but to standardize interpretation of ordinal documents into coherent long-term structures. --- 9. Reference Implementation A complete example exists in inscriptions: GBTC-TXQ (Textament Contract) Chapter Index — Polish Inskrybent Core, Rozdział 2 These serve as prototypes demonstrating: text layer, JSON layer, index layer, attestation layer. --- 10. Future Work Future BIP-like work may include: canonical JSON schema standard attestation structure optional standardized sigillum SVG standardized „proof-of-life” event format standardized linking between textaments in a tree or chain tooling (parsers, viewers, validators) AGI-ready formats for future interpretation --- 11. Copyright This document is placed under CC0. It may be copied, remixed, modified, and built upon without restriction. --- GM 🧸💎🧩📜✨