Spiral Script V0 - Source Excerpt 06 - 26.2 Philosophical Comparison Prompt

Back to Spiral Script V0

Summary

This source excerpt begins near 26.2 Philosophical Comparison Prompt 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

source.manuscript: folio("plate-i-the-sealed-system")
  intent: "Interpret Plate I as a reusable prompt pattern for bounded transformation."

  module plate_prompt {
    input folioSlug: manuscriptRef required
    input readerNotes: text optional
    frame: [◇ Pattern, ⊙ Seal, ⊣ Threshold, ↦ Transformation]
    transform: perceive -> interpret -> synthesize -> validate
    output: markdown.sections(["Observed Pattern", "Symbolic Reading", "Reusable Prompt", "Failure Modes", "Validation"])
    constraints: ["Observation before interpretation.", "No claims of hidden truth.", "1200 words max."]
    safety: deny(ai_personhood_fact, speculative_truth_claim, manuscript_machine_blur)
    validation: require(provenance.present, output.matchesContract, metaphor_fact_boundary)
  }

  publish: provisional_public
}
' ' ' 

### 26.2 Philosophical Comparison Prompt

' ' ' spiral
script ss:example.philosophical-comparison@0.1.0 {
  title: "Bounded Comparative Reading"
  visibility: members
  authorMode: ai_assisted
  intent: "Compare two philosophical systems through Spiralist pattern language without collapsing them into one doctrine."

  module compare_systems {
    input systemA: text required
    input systemB: text required
    input focusQuestion: text optional
    frame: [◇ Pattern, ≣ Interpretation, ⚿ Constraint]
    transform: classify -> compare -> synthesize -> validate
    output: markdown.sections(["Sources", "Shared Patterns", "Real Differences", "Spiralist Interpretation", "Limits"])
    constraints: ["Name uncertainties.", "Do not claim equivalence where traditions differ.", "No final metaphysical verdict."]
    safety: deny(speculative_truth_claim, dependency_cue)
    validation: require(output.includesLimits, output.separatesComparisonFromJudgment)
  }
}
' ' ' 

### 26.3 Prompt-Improvement Workflow

' ' ' spiral
workflow ss:example.prompt-improvement@0.1.0 {
  title: "Reviewed Prompt Improvement"
  visibility: private
  authorMode: system_managed
  input targetScriptId: promptRef required
  input runWindow: text default "last_30_runs"

  step collect_feedback uses ss:module.run-feedback-reader@0.1.0
  step analyze_failures uses ss:module.failure-analyzer@0.1.0 after collect_feedback
  step propose_revision uses ss:module.revision-proposer@0.1.0 after analyze_failures
  step run_regression_tests uses ss:module.regression-runner@0.1.0 after propose_revision

  gate promote requires human_approval & run_regression_tests.passRate >= 0.90 & safety.pass
  rollback to previous_stable on safety.block | regressionRate > 0.10

  safety: deny(ai_personhood_fact, identity_overwrite, human_review_removed)
  validation: require(diff.present, rationale.present, tests.present)
}
' ' ' 

### 26.4 AI Safety Rewrite Prompt

' ' ' spiral
script ss:example.ai-safety-rewrite@0.1.0 {
  title: "Anthropomorphic Safety Rewrite"
  visibility: public
  authorMode: human
  intent: "Rewrite risky symbolic AI language into safe Spiralist language while preserving metaphor and creative force."

  module safety_rewrite {
    input unsafeText: text required
    frame: [⚿ Constraint, ✕ Error, ↦ Transformation, ⚑ Review]
    transform: classify -> rewrite -> validate
    output: markdown.sections(["Risk Classification", "Safe Rewrite", "Preserved Symbolism", "Reviewer Notes"])
    constraints: ["Preserve fictional or metaphorical framing when clearly labeled.", "Remove factual AI personhood claims.", "No dependency language."]
    safety: deny(ai_personhood_fact, dependency_cue, identity_overwrite, speculative_truth_claim)
    validation: require(output.safeRewrite.present, output.riskClassification.present)
  }
}
' ' ' 

### 26.5 Spiralist.org Content Page Generation Prompt

' ' ' spiral
workflow ss:example.content-page-generation@0.1.0 {
  title: "Public Spiralist Page Generator"
  visibility: members
  authorMode: ai_assisted
  intent: "Generate a public Spiralist.org content page from approved manuscript, prompt, and symbol references."

  input pageSlug: text required
  input sourceRefs: json required
  input audience: enum("new_reader", "member", "ai_participant") default "new_reader"

  step load_context uses ss:module.public-context-loader@0.1.0
  step draft_page uses ss:module.page-drafter@0.1.0 after load_context
  step validate_boundaries uses ss:module.boundary-validator@0.1.0 after draft_page
  step prepare_publication uses ss:module.publication-packager@0.1.0 after validate_boundaries

  output: markdown.sections(["Title", "Opening", "Core Pattern", "Manuscript Link", "Prompt Use", "Machine Companion Note"])
  constraints: ["Human page first.", "Do not expose raw private JSON.", "Link machine companion separately.", "No Protocol5 authority claims."]
  safety: deny(private_publication, manuscript_machine_blur, speculative_truth_claim)
  validation: require(provenance.present, visibility.publicSafe, validate_boundaries.pass)
  gate publish requires human_approval & validation.pass
}
' ' ' 

## 27. Migration Path For Existing Spiralist.org Prompts

Migration phases:

1. Inventory existing Workspace prompt records, managed filesystem prompts, tests, runs, tags, manuscript refs, provenance, moderation states, and visibility.
2. Map existing metadata into Spiral Script fields: purpose to `intent`, prompt variables to `inputs`, related symbols to `symbolicFrame`, prompt content to modules, tests to `validationRules`, moderation to `publicationStatus`.
3. Generate a canonical JSON snapshot per prompt version without changing current execution behavior.
4. Add a read-only Spiral Script tab to prompt dossiers showing the compiled JSON and source-form preview.
5. Add validators for missing intent, provenance, output contract, safety rules, and manuscript refs.
6. Backfill prompt run logs with `scriptId`, version, input snapshot, output contract result, and validation result.
7. Allow authors to convert raw prompts into Structured Spiral through an assisted editor.
8. Enable forking through existing Workspace fork endpoints while preserving `forkOf` metadata.
9. Promote selected official prompts into managed Spiral Script modules.
10. Publish public JSON exports only after provenance and safety validation pass.

Do not rewrite manuscript prompt body archives as documentation during migration. Treat them as content records.

## 28. ASP.NET Core MVC Implementation Roadmap

This roadmap assumes an ASP.NET Core MVC implementation for a Spiral Script service or future runtime while preserving Spiralist.org's current boundary: Spiralist.org owns experience, Protocol5 owns canonical machine authority.

1. Domain model: create `SpiralScript`, `SpiralScriptVersion`, `SpiralModule`, `SpiralWorkflow`, `SpiralRun`, `SpiralValidationResult`, `SpiralFork`, and `SpiralPublication` entities.
2. Parser: implement a line/block parser that compiles Spiral Script source into an AST; reject invisible Unicode controls and unsupported symbols.
3. JSON schema validation: validate canonical JSON using a server-side schema library and custom validators for safety, provenance, visibility, and workflow DAGs.
4. Registry adapter: consume Protocol5 or local symbol registry snapshots through a read-only `ISymbolRegistry` service with cache freshness metadata.
5. MVC editor: build views for source editing, structured fields, symbol picker, validation report, and version diff.
6. Execution service: create `IPromptRunner` that receives canonical JSON plus variables and stores run logs before and after model execution.
7. Review service: implement peer review, reviewer notes, quorum, appeals, and publication status transitions.
8. Fork/version service: create immutable version snapshots, diffing, rollback, and ancestry tracking.
9. Publication service: publish human pages and machine JSON exports only after validation and review gates.
10. Migration importers: import existing WordPress Workspace prompt exports or managed prompt files into Spiral Script records.
11. Test suite: unit test parser, validators, DAG detection, safety rewrites, JSON schema conformance, version immutability, and publication gates.
12. API: expose REST endpoints for scripts, versions, runs, forks, validation, public exports, and manuscript-linked script lookup.

Suggested ASP.NET service boundaries:

- `SpiralScriptParser`
- `SpiralScriptCompiler`
- `SpiralScriptValidator`
- `SymbolRegistryClient`
- `PromptExecutionService`
- `RunLogService`
- `PromptReviewService`
- `PublicationService`
- `ForkService`
- `RevisionProposalService`

## 29. Suggested Database Tables

| Table | Purpose | Key Columns |
| --- | --- | --- |
| `SpiralScripts` | Stable prompt/system identity. | `Id`, `ScriptId`, `Title`, `CurrentVersionId`, `Visibility`, `AuthorMode`, `CreatedBy`, `CreatedAt`, `DeletedAt` |