rtd: imperial_frame out of packet example (ruling) + DRAFT Dao path-fit ontology (proposal, not canon) #6
Loading…
Reference in a new issue
No description provided.
Delete branch "weksa/rtd-imperial-frame-ontology-side"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Two parts, both rust-to-dust proposals, neither canon.
settings/rust-to-dust/language-design.mdno longer showsimperial_framein the client packet example, per rulingweksa-body:ruling:rtd-imperial-aesthetic-reading-to-ontology(2026-11-05). The example carries neutral facts plus stance; the old value is the ontology's output.imperial/dao-ontology.md(new, DRAFT r0, "nothing here is canon") proposes a path-fit value system for the empire, andimperial/language-design.mdpoints at it. The edited lines there are marked PROPOSAL, not canon, and "unpainted" is re-framed from shamelessness to fit against the actor's path.Credit: Meta (#weksa, 2026-11-06) supplied the Dao placeholder name, the path-fit norm-breaking examples and the Dao De Jing analogy; Deru's 2026-11-06 name rules do not touch this PR except one respelling (Sa'ueia) that landed with PR 9. Chat memory ids were removed from the draft; Meta's words are paraphrased.
Review fixes (Nibu): scope stated, edited lines marked proposal, full ruling id given, with_scene dependency resolved (PR 8 merged).
Open: does "authentic local defiance" survive as an ontology class; are the example stance grades sensible.
🤖 Generated with Claude Code
Review (nibu, read-only, follow-up
chat-s3380-3381). Verdict: safe after named fixes.Checked: diff vs title, canon/proposal separation, ruling ids, backslash wikilinks / table pipes (none: markdown links only, no pipes inside table cells), workflow files (none touched).
imperial/dao-ontology.mdand rewrites the "unpainted" semantics inimperial/language-design.md(L76-80, L87-90, L186-192, L271-274): "shameless" becomes "heresy against Dao". That is a setting-design proposal, not an example correction. Fix: say so in the title/body, or split the example fix (rust-to-dust/language-design.mdonly) from the Dao ontology.dao-ontology.mdsays "Nothing here is canon", butimperial/language-design.mdnow states the re-framing in its body, tagged[E→I]. The two files disagree on status. Fix: leave the existing doc's text alone and put a pointer to the draft, or mark the edited lines as a proposal.rust-to-dust/language-design.mdcitertd-imperial-aesthetic-reading-to-ontology.huginn view weksa-body:ruling:rtd-imperial-aesthetic-reading-to-ontologyreturns absent. Please give the full id or the doc where it lives. The id is cited correctly in form; I just can't confirm it exists.dao-ontology.mdsection 4 points atLoweringInput::with_scene, which only exists in PR #8 (unmerged). Merge #8 first or reword.dao-ontology.md"How To Read This" cites memory ids and quotes Meta's #weksa words from 2026-11-06. Confirm Meta is fine with that being in the repo, or paraphrase without the ids.No canon file is edited (
aliens.mdis explicitly left alone), and no deploy/workflow files are touched.Not merged. #8 has now landed, so finding 4 (with_scene) is resolved. Still open and not mine to decide: (1) scope vs title, split the example fix from the Dao ontology or retitle; (3) the ruling id rtd-imperial-aesthetic-reading-to-ontology, whoever holds it must give the full id; (5) Meta must OK the chat provenance in a public repo. Needs the setting owner and Meta.
rtd: imperial_frame is an ontology reading, not a packet fieldto rtd: imperial_frame out of packet example (ruling) + DRAFT Dao path-fit ontology (proposal, not canon)