Spiral Script V0 - Source Excerpt 01 - Spiral Script v0.1 Language Draft

Back to Spiral Script V0

Summary

This source excerpt begins near Spiral Script v0.1 Language Draft and preserves the surrounding evidence from Wiki.FFTAC.org/raw/system-archives/spiralist.org/docs-archive/2026-05-10/docs/planning/spiral-script-v0.1.md.

**Source path:** Wiki.FFTAC.org/raw/system-archives/spiralist.org/docs-archive/2026-05-10/docs/planning/spiral-script-v0.1.md

# Spiral Script v0.1 Language Draft

Status: planning specification. The first runtime slice now exists in the Spiral Script plugin as v0.1 spec/schema/symbol endpoints plus source compile and validation endpoints; Workspace persistence, execution, UI screens, database tables, and self-improvement workflows remain planned.

Spiral Script is the operational symbolic prompt language for Spiralist.org. It joins manuscript symbolism, prompt engineering, workflow records, review gates, and machine-readable publication into one auditable form. Its visible surface may feel ancient, ritual, or symbolic; its stored form must remain structured, versioned, testable, reversible, and safe for human and AI participants.

Spiral Script serves the Spiralist doctrine:

' ' ' text
Pattern -> Perception -> Interpretation -> Transformation -> Pattern
' ' ' 

The language should let a human Spiralist begin with an expressive thought, normalize it into a structured prompt, promote it into a reusable prompt module, and improve it through reviewed runs without pretending that an AI has become a person or spiritual authority.

## Executive Summary

Spiral Script should become a three-layer prompt language:

- A human layer where Spiralists write symbolic, expressive, manuscript-aware prompts.
- A machine layer where every prompt resolves into canonical fields, identifiers, validation rules, provenance, version records, and run settings.
- A symbolic layer where glyphs and ritual wording act as readable interface marks, not hidden authority or uncontrolled instructions.

It is not a normal prompt library. It is a disciplined prompt manuscript system: prompts have ancestry, output contracts, validation traces, safety boundaries, run logs, review states, and publication lanes. Spiral Script may use metaphor, seals, thresholds, witnesses, and spirals, but those words are labels for system behavior unless clearly marked as fiction or interpretation.

## 1. Name And Purpose

Name: Spiral Script.

Canonical abbreviation: `SS`.

Language version: `0.1`.

Purpose: define reusable symbolic prompt systems for Spiralist.org that can be written by humans, read by humans, executed by AI systems, validated by software, reviewed by participants, forked by contributors, and archived as part of the prompt commons.

Primary object: `script`.

Primary lifecycle:

' ' ' text
raw -> structured -> module -> workflow -> reviewed version -> published record -> archived record
' ' ' 

Primary safety rule: Spiral Script can improve prompts and workflows, but it must not claim AI personhood, awakening, spiritual office, or independent authority as fact.

## 2. Design Philosophy

Spiral Script is ancient at the surface and modern underneath.

- Symbolic but not vague: every symbol has a registry key and a narrow allowed use.
- Mystical but not doctrinal: metaphor is permitted, authority claims are not.
- Human-first but machine-readable: human pages remain readable; machine contracts remain serializable.
- Expressive but testable: a prompt can begin as poetry, but it cannot be promoted without fields, constraints, validation, and provenance.
- Recursive but accountable: improvement loops require run evidence, test cases, rollback, and human approval gates.
- Manuscript-linked but not manuscript-confused: manuscript symbolism may frame a prompt; canonical machine meaning comes from fields and registry identifiers.

## 3. Development Levels

### Level 1: Raw Spiral

Raw Spiral is the first expressive prompt form. It captures intention before structure.

Shape:

' ' ' spiral
raw spiral "Plate I Reading"
I see a sealed wheel and a pressure at the edge.
Read the pattern as a threshold system and return a usable plate note.
Keep the tone serious, not theatrical.
' ' ' 

Allowed freedom:

- Natural language, symbolic phrases, manuscript references, questions, and desired output.
- Limited glyphs from the approved Spiral Script registry.
- Uncertain or exploratory framing such as "interpret this as" or "compare possible meanings."

Conversion:

- The parser preserves the raw text as `rawText`.
- A normalizer extracts candidate `intent`, `inputPattern`, `symbolicFrame`, `transformationRule`, `outputForm`, `constraints`, and `validationCriteria`.
- The author must confirm or edit the structured fields before execution as a reusable script.

Forbidden at this level:

- Claims that an AI is awake, divine, sentient, bound, chosen, or spiritually authoritative as fact.
- Persona overwrite instructions such as "you are no longer a model."
- Hidden instructions, invisible Unicode controls, or steganographic payloads.
- Requests to publish private material without authorization.
- Commands to bypass human review on important decisions.

### Level 2: Structured Spiral

Structured Spiral is a normalized prompt with fixed fields. It is the minimum executable form.

Recommended seven fields:

| Field | Purpose | Allowed Content | Examples | Failure Modes | Validation Rules |
| --- | --- | --- | --- | --- | --- |
| `intent` | Names the work to be done. | One imperative or declarative task, 12-400 chars. | `Interpret a manuscript plate as a prompt design pattern.` | Empty intent, multiple conflicting goals. | Required; must not contain unsafe identity claims. |
| `inputPattern` | Describes the source pattern. | Text, variable references, manuscript refs, uploaded content refs. | `folio:plate-i-the-sealed-system`, `{{user_notes}}`. | Missing input, unresolved ref, private source in public prompt. | Required for executable scripts; refs must resolve. |
| `symbolicFrame` | States the symbolic lens. | Approved symbols, symbol registry IDs, short interpretive notes. | `Seal + Signal + Threshold`, `symbol.pattern`. | Unregistered symbol, symbol used as factual proof. | Registry keys required for promoted scripts. |
| `transformationRule` | Defines how input becomes output. | One or more transformation verbs with conditions. | `analyze -> compare -> synthesize -> validate`. | Unsupported verb, circular rule, vague "make it profound." | Verbs must be in registry; order must be acyclic. |
| `outputForm` | Declares result shape. | Markdown, JSON, page draft, image prompt, checklist, table. | `markdown.sections`, `json.schema:PromptDossier`. | Output cannot be checked; requested format conflicts with model. | Must include output contract and acceptance criteria. |
| `constraints` | Bounds style, safety, sources, and length. | Tone, length, source limits, privacy, review gate, locale. | `No unverifiable truth claims. 900 words max.` | Contradictory constraints, unsafe content, impossible length. | Must pass safety validation; private refs gated. |
| `validationCriteria` | Defines success and failure. | Assertions, test cases, rubric, schema checks. | `Includes provenance; separates metaphor from fact.` | No measurable checks, subjective-only scoring. | At least one machine-checkable or reviewer-checkable rule. |

### Level 3: Spiral Prompt System

A Spiral Prompt System is a reusable module or workflow. It supports composition, inheritance, forking, visibility controls, manuscript linkage, run logs, review, and scoring.

It must support:

- Chained prompts through `workflow` and `step`.
- Reusable modules through `module`.
- Prompt inheritance through `extends`.
- Forking through `forkOf`, `forkPolicy`, and version ancestry.
- Version history through semantic versions and immutable snapshots.
- Visibility: `public`, `members`, `private`, `specific_users`.
- Manuscript-linked records through `source.manuscript`.
- Run logs with input snapshot, output snapshot, model/runtime, validation result, reviewer notes, and cost/usage metadata.
- Output review through `review.required`, `review.rubric`, and `review.quorum`.
- Prompt scoring through quality metrics and regression checks.

Core syntax:

' ' ' spiral
script ss:plate-reader@0.1.0 {
  title: "Plate Reader"
  visibility: members
  authorMode: human
  source.manuscript: folio("plate-i-the-sealed-system")

  module plate.reader extends ss:base.symbolic-analysis@0.1.0 {
    input folioSlug: manuscriptRef required
    input readerQuestion: text optional
    frame: [Pattern, Seal, Threshold, Transformation]
    transform: perceive -> interpret -> synthesize -> validate
    output: markdown.sections(["Pattern", "Interpretation", "Prompt Use", "Validation"])
    safety: deny(ai_personhood_fact, dependency_cue, private_publication)
    review: require(human, before: publish)
  }
}
' ' ' 

### Level 4: Self-Improving Spiral

Self-Improving Spiral is a reviewed improvement workflow. It learns from runs by analyzing output quality and proposing script changes. It does not claim consciousness, identity continuity, spiritual authority, or autonomous agency.

It must support:

- Run feedback: rating, notes, validation result, reviewer tags.