SERA — Structural Edit Resolution and Admission
Structural Keyboard · Human Reference Surface
Clipboard: empty
SERA is the admission boundary; Structural Keyboard is the human reference surface. generated edit != admitted edit · document changed != proposal automatically stale · Required structural dependencies, not whole-document change alone, govern whether prepared edit authority may survive.
Current target Resolve a structural target
Pre-commit classical plan Hover or focus an editing action to preview its exact canonical plan.
Admission contract No admitted plan preview —
Structural position Sentence 1 of 1
No target snapshot
Click or move the caret, then choose a scope. Use ← and → to navigate between resolved structural units. Use ⇤ and ⇥ to move the current unit. Manual text edits preserve the previous target snapshot so the STALE gate can be demonstrated at commit time.
Choose a scope or click in the editor to resolve a structural target.
SERA · Structural Keyboard

Quick Guide

You only need to remember one idea: choose the size of the text you want to work with, then use the familiar editing buttons.

1
Click in the documentPlace the editing focus near the word, sentence, or paragraph you want.
2
Choose a ScopeSelect GRAPHEME, CODE POINT, WORD, SENTENCE, PARAGRAPH, or another available structural level.
3
Move between unitsUse ← and → to go to the previous or next unit. These arrows do not change the document.
4
Edit the whole unitUse Cut, Copy, Paste, Delete, Duplicate, ⇤, or ⇥. Paste places the copied text after the current structural unit.
5
Watch the stateRESOLVED means one target is clear. AMBIGUOUS means you can choose a candidate. STALE means the earlier target changed and the edit is safely refused.
6
Use the keyboard directlyAlt + ←/→ navigates, Alt + Shift + ←/→ moves text, Alt + ↑/↓ changes scope, and Alt + 1/2/3 chooses an ambiguity candidate.
7
Save or export evidenceUse 💾 or Ctrl + S for the document. The Receipts tab can export the genesis content, profiles, receipts, final hash, and chain head as JSON.
← → Navigate ⇤ ⇥ Move text ✂ Cut ⎘ Copy 📋 Paste ⌫ Delete ⧉ Duplicate ↶ ↷ Undo / Redo Alt + ↑ ↓ Scope Alt + 1/2/3 Choose ? Keymap
Demonstrations and Audit
For the complete release regression gate, run await SERA_AUDIT.runAll(). Full-audit coverage is preserved across later quick and focused checks. Use SERA_AUDIT.lastFull() for the archived full result, SERA_AUDIT.coverage() for persistent feature coverage, and SERA_AUDIT.inspect() for the current structural state.
Project and Resolver Information
Anyone may propose. Structure resolves. Admission permits. Evidence records.
Structural Keyboard is the reference human interaction surface for SERA — Structural Edit Resolution and Admission.
proposal -> resolve -> plan -> preview -> revalidate -> admit -> execute OR refuse -> receipt
Self-test: running… Rules: SK-RULES-1.1.0 Proposal: SERA-PROPOSAL-1-D01 Preview: SERA-PREVIEW-COMMIT-2-D01 Receipts: SERA-RECEIPT-2 Refusal: SERA-REFUSAL-WITNESS-1-D01 Grapheme: Unicode 17.0.0 Admission: SERA-ADMISSION-DEP-1-D01
Authority separation: proposal authority, target authority, and mutation authority remain separate.
No Silent Retarget: if the target fingerprint changes after preview, the old commitment cannot authorize a newly resolved target.
Strict agent mode: a machine-supplied range is treated as a locator hint, never as automatic mutation authority.
Refusal witness: AMBIGUOUS, UNSUPPORTED, STALE, and CONFLICT outcomes can record deterministic non-mutation evidence.
Dependency-aware admission: unrelated document changes need not invalidate a proposal; changes to required target, context, or destination structure do.
Relevant Change Principle: unrelated change must not automatically invalidate valid edit authority, while dependency-changing mutation must not silently preserve old authority.
Structural Admission Survival: a prepared proposal may remain admissible after the document changes when its resolved target, declared dependencies, canonical plan, and admitted write boundary remain valid.
Mutation envelope: every admitted canonical plan is bounded to its declared write region.
Structural edit permit: an admitted plan receives a deterministic single-use permit bound to target, dependencies, plan, and mutation envelope.
Fingerprint profile: SK-FP-HYBRID-1-D01 binds scope, structural path, target content, and bounded neighbouring context.
Offset contract: the current browser implementation uses UTF-16 code-unit offsets. The browser exposes both GRAPHEME and CODE_POINT. Grapheme resolution follows the frozen SERA-UNICODE-GRAPHEME-1-D01 profile while evidence offsets remain UTF-16 code units.
No final punctuation: the paragraph resolves as one sentence.
Period, question mark, exclamation mark: terminal when followed by whitespace or paragraph end.
Multiple spaces: accepted as boundary spacing and preserved by structural movement.
Missing space after a likely sentence-ending period: returns AMBIGUOUS instead of silently splitting.
Semicolon and colon: remain inside the sentence under this frozen rule profile.
Known abbreviations and non-terminal ellipses: can return AMBIGUOUS.
Decimals and internal dotted forms: are not treated as sentence boundaries by default.

🔎 Structural Inspector

Scope-aware resolution and evidence
Schema
Rules
SK-RULES-1.1.0
Scope
Anchor
Target state
Resolution mode
Candidate set
Target span
Fingerprint
FP profile
SK-FP-HYBRID-1-D01
Offset unit
UTF16_CODE_UNIT
Admission profile
SERA-ADMISSION-DEP-1-D01
Dependency state
Dependency fingerprint
Plan hash
Envelope profile
SERA-MUTATION-ENVELOPE-1-D01
Envelope hash
Permit
Preview commitment
Resolve a target and preview a mutating action to see its dependency-aware admission contract.
The document hash may change while a proposal remains admissible if its declared structural dependencies and canonical plan remain unchanged.
No structural action yet.
Resolve a target and choose an action to see the canonical classical edit plan.
The planning layer converts structural intent into a canonical classical edit plan. Planning is distinct from the Shunyaya collapse operator and remains inspectable before mutation.
Chain head: —
Verification in this page is producer-side. The exported bundle is designed for a separate verifier.

🧪 Verification

The built-in checks cover deterministic resolution, explicit ambiguity, canonical proposal identity, strict agent range-hint handling, No Silent Retarget, human-readable refusal explanations, grapheme and code-point scopes, multilingual demo content, Tamil and emoji vectors, target and admission fingerprints, structural relevance classification, Structural Admission Survival, dependency-aware concurrency, the Admission Boundary Matrix, mutation envelopes, structural edit permits, preview v2 binding, deterministic refusal witnesses, receipt-chain integrity, verifier fixtures, and replay identity.

Reference Only · Shunyaya Framework

🧩 Boundary Challenge

Load the challenge text and select SENTENCE. The frozen rules intentionally treat selected abbreviation boundaries as ambiguous. An attempted mutation produces a non-mutating refusal receipt instead of silently guessing.

🔁 Schema Portability

Switch between TEXT and MARKDOWN. The action grammar stays familiar while the available structural scopes change. Markdown adds LIST_ITEM and SECTION.