S³SSSP
繁體中文

EVEMISSLAB / RESEARCH MVP · v0.2

The source survives the conversation.

SSSP is an AI-native protocol for scholarly writing. It gives agents typed nodes, revisions, checksums and validation—so canonical source is edited directly, while Markdown and rendered pages remain derived views.

Explore the protocol View source

The invariant

  1. 01Discussion
  2. 02Canonical source
  3. 03Validation
  4. 04Rendered views

01 / THE FAILURE MODE

Render success is not source integrity.

A page can look correct while the expression underneath it has already changed. SSSP moves validation in front of the commit instead of asking a repair pass to guess the source later.

01

Copied view

Canvas or DOM output is copied instead of the original LaTeX source.

02

Silent escape

Sequences such as \b, \t or \n are decoded into control characters.

03

Cascade repair

A broad repair regex fixes one delimiter and damages valid TeX elsewhere.

×Rendered view → copy → guess source → repair
✓Discussion → canonical source → validate → render

02 / PROTOCOL ANATOMY

One source. Deliberately different views.

The canonical document is a typed, revisioned object. Exports are compiled from it; the audit trail records how it changed. Use the controls to inspect the same node through each lens.

Canonical sourceeq-0001
{
  "id": "eq-0001",
  "type": "math_block",
  "latex": "\\forall x\\in X,\\;P(x)",
  "checksum": "sha256:4b8c…e21f"
}

Typed data is authoritative. Delimiters are not part of the math payload.

01

Canonical format

Typed scholarly nodes plus semantic and claim ledgers.

02

Mutation protocol

Create, append and replace operations guarded by revisions and checksums.

03

MCP adapter

A seven-tool interface over stdio or basic Streamable HTTP.

03 / EXECUTABLE SURFACE

Seven tools, one authority boundary.

Agents mutate the canonical document through explicit operations. Read, validation, export and snapshot remain named steps rather than invisible side effects.

Mutate

  • sssp.create_documentCreate a canonical document.
  • sssp.append_nodeAppend one typed node, then validate before atomic commit.
  • sssp.replace_nodeReplace one node with revision and checksum conflict protection.

Inspect

  • sssp.read_nodeRead canonical data without going through a rendered export.
  • sssp.validate_documentRun structural, character and MathJax validation.

Derive

  • sssp.export_documentCompile a derived Markdown view.
  • sssp.commit_versionCreate an immutable validated snapshot.

Validation is layered—and its boundary is named.

L1

Structural / character

implemented

Control bytes, PUA, zero-width markers, checksums, duplicate IDs and basic TeX structure.

L2

Renderer

implemented

MathJax parses each canonical math block before a validated snapshot is created.

L3

Semantic

planned

Claim consistency, symbol drift and semantic diff remain research work—not present-tense guarantees.

04 / STATUS & BOUNDARIES

A research MVP that says where it stops.

SSSP v0.2 is executable and tested. It is not yet a production multi-writer scholarly service. The public site explains the protocol; it does not expose an unauthenticated write endpoint.

●

Available now

  • Typed canonical documents and ledgers
  • Revision and checksum conflict protection
  • L1 structural and L2 MathJax validation
  • Immutable snapshots and Markdown export
  • MCP over stdio and basic Streamable HTTP
○

Not claimed yet

  • OAuth/OIDC authorization
  • A multi-writer lock service
  • Full runtime JSON Schema enforcement
  • An L3 theorem or meaning checker
  • Production persistent scholarly storage

REFERENCE IMPLEMENTATION

Run the reference implementation

Clone the repository, install the pinned MathJax dependency, then start the local MCP server.

Read the deployment notes
powershell
git clone https://github.com/kakon77777-commits/SSSP.git
cd SSSP
npm install
python src/mcp_server.py