Skip to content

Latest commit

 

History

History

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

README.md

Chiral Narrative Synthesis 8.0

Grounded Dialectical Orthesis

This docset defines Chiral Narrative Synthesis 8.0 (CNS 8.0).

CNS 8.0 uses the original CNS sequence:

conflicting narrative objects
→ chiral opposition
→ evidential entanglement
→ antagonist pressure
→ proof-grounded tensor closure
→ contradiction residuals
→ predicate invention
→ synthesized SNO
→ orthesis candidate
→ audit / uncertainty report

The evidence/access/possible-world machinery is included only as a constraint and reporting substrate. It does not replace narrative synthesis.

Package map

  • TOC.md — source table of contents.
  • docs/ — research proposal, theory, architecture, implementation, experiments, and contribution analysis.
  • schemas/ — JSON schemas for SNO-8, evidence atoms, proof traces, and orthesis reports.
  • sketches/ — small Python sketches for the computational components.
  • configs/ — MVP config and runtime policy examples.
  • experiments/ — experiment matrix and ablation suite.
  • prompts/ — bounded LLM role prompts.
  • examples/ — worked example of CNS 8.0 resolving a conflict.
  • refs/ — annotated references and BibTeX.

Naming rule

Use Chiral Narrative Synthesis or CNS 8.0 for the work. Do not rename the framework around any grounding subsystem.

What CNS 8.0 preserves

  • Structured Narrative Objects as the main data object.
  • Dialectical roles: Proposer, Antagonist, Synthesizer, critic ensemble.
  • Chirality as structured asymmetry, not generic disagreement.
  • Evidential Entanglement as the conflict selector.
  • Orthesis as stable synthesis candidate / fixed point.
  • Tensor logic as proof-carrying synthesis substrate.
  • Predicate invention as contradiction-driven hidden-context discovery.
  • Topology / holonomy as diagnostics of synthesis difficulty.
  • Grounding, access states, possible worlds, oracle boundaries, and audit trails as constraints.

Version

Prepared: 2026-05-15
Status: research proposal + implementation plan + test plan, not full production code.