Skip to content

Living paper v0.1-dev: evidence, author input, and linked practice - #6

Closed
raelovejoy wants to merge 6 commits into
mainfrom
coherent-systems-living-paper-v0.1-2026-09-16
Closed

raelovejoy wants to merge 6 commits into
mainfrom
coherent-systems-living-paper-v0.1-2026-09-16

Conversation

@raelovejoy

@raelovejoy raelovejoy commented Sep 16, 2026 •

Copy link
Copy Markdown
Collaborator

Current status and resume point

Latest development commit: 5c15f7fecd96924b9a18f6ff49d2cb01f2568dd0. This is a public draft, not a reviewed release. No merge, deployment, DOI, or manuscript approval is included.

The paper remains at research/papers/coherent-systems/. Subsequent author-input and workflow passes are recorded in its changelog and PR comments. The author-requested explanation of AI as both an accessibility aid and a development tool is already in AI-ASSISTANCE.md; it was preserved in this pass.

Resume at section 4 / C-003, with C-006's safeguard discussion. The author distinguished situated reasoning from target compliance and actual fit, and asked for consequences and alternatives to be visible without blaming people who lack information, resources, or authority. The remaining question is how to assess a coherent response when capacity still cannot meet all needs. No answer or new definition is inferred from a request to route insights. T-003 remains unrun.

Latest pass: fill gaps in existing work

Four existing files changed:

  • core/legible-systems.md: supported participation, sensemaking, transferred review burden, and dependency-aware iteration; a source/application table for five W3C documents plus the publisher abstract of Weick, Sutcliffe, and Obstfeld (2005).
  • THOUGHT_ROUTING.md: the author's clarification to build on existing work and identify actual gaps rather than defaulting to new frameworks; return to the active question after routing.
  • research/papers/coherent-systems/AGENTS.md: apply that instruction and keep review context manageable.
  • research/papers/coherent-systems/CHANGELOG.md: what changed and the precise re-entry point.

No new files, frameworks, taxonomies, or repositories. The manuscript, claim ledger, AI-use explanation, UCF model, bibliography, code, and website were not changed in this pass. The human-scale Atlas application is maintained separately; no private source text or personal health details were imported here.

W3C editions, document status, and inspected sections are recorded with limits. Cognitive guidance is supplemental to WCAG; the sustainability document is a Group Note Draft; Statements, Notes, and empirical research are not treated as interchangeable evidence. These are existing sources and proposed applications, not validated results for our workflow.

Verification in this pass: inspected the before/after Git comparison and patch. Changes are additions; the reported one-line removal in core/legible-systems.md is the unchanged final sentence acquiring a newline before the appended section. Existing content was not removed. New local destinations were checked against the fetched files and heading text; no full-repository link audit, software test run, empirical study, or replication was performed.

Earlier external-evidence pass and verification record (historical; preserved)

Current scope

Canonical paper source remains research/papers/coherent-systems/. Latest development commit: 017455f14e1b1d2b3cb592df53131ce4cab2b52e.

Status: v0.1-dev, AI-assisted, substantive author review pending, not peer reviewed. This PR remains a public draft. No merge, release approval, deployment, DOI, or approved personal byline is included.

External-evidence pass — September 16, 2026

Added three documents:

  • Related-work comparison: scoped comparison with STPA, sociotechnical abstraction, values alignment, full-stack alignment, and a published empirical case; candidate T-003 comparison design, not an executed study.
  • Healthcare cost-proxy case: attributed findings from Obermeyer and colleagues (2019), our retrospective questions, and explicit limits. The 17.7% to 46.5% result is simulated reallocation of the auto-identified group, not measured post-deployment improvement or the percentage of all Black patients served.
  • AI-assistance and author-review record: substantive drafting, comparison, research organization, and earlier code assistance disclosed; source inspection, software checks, human author review, and independent evaluation distinguished.

Revised C-001, C-003, C-005, and C-012, manuscript sections and citations, the abstract, bibliography, source map, charter, research-task status, and changelog. C-003 now distinguishes interacting functional and normative questions, not independent stages in which value-free engineering precedes ethics. Shared prior work is not claimed as a new discovery.

The manuscript retains twelve numbered sections and twelve provisional claims. The abstract is 202 whitespace-delimited words. The research bibliography has eight entries: seven external research/method sources and one internal UCF source. Elsevier's policy is cited separately as editorial context, not research evidence or an acceptance guarantee.

Reading coverage and evidence boundaries

The source map records exact versions, sections/pages inspected, screenshots used, and remaining gaps. Reading was targeted and AI-assisted, not a systematic literature review or completed human author reading. No cited study was independently replicated. No raw patient records, confidential manuscripts, or third-party full papers/figures were copied into this repository.

The published case is not a UCF discovery and does not validate its universality or added value. STPA is a candidate comparison method where appropriate; the proposed plan requires baseline fidelity, equivalent information, and transparent effort accounting. The existing three booking allocation rules are not three review methods.

Checks performed in this pass

  • Verified the eight original paper-file blobs from the portable snapshot against the existing Git revision before editing.
  • Ran 20 local structural checks: exact ten-file change scope, preservation, twelve sections/claims, ten questions, three task identifiers, eight manuscript footnotes, eight unique bibliography keys, basic brace balance, draft/review labels, author-review checkboxes, and discoverability.
  • Checked 61 relative Markdown link occurrences in the changed files against local files or explicitly connector-verified repository paths; checked two explicit local heading anchors. This is not a complete repository or external-link audit.
  • Read back the prepared research tree and matched all ten changed Git blob hashes to the inspected local files.
  • Compared the new commit with its parent: only the ten intended paper-directory files changed, with three additions and seven modifications. No file was deleted; prior meaning and revisions remain traceable through the changelog and Git history.

No full BibTeX rendering, website build, empirical experiment, participant study, or booking-model rerun was performed in this external-evidence pass. Structural checks are not scholarly validation.

Prior UCF reconciliation retained

The earlier paper reconciliation is commit 20740c794a5a01b2d616abc6f74bad9dcf83054d, linked to UCF draft PR #2. The manuscript cites UCF model/code content revision c4d7b236828a59139c0d5204b1faaed13154682a. The current pass did not modify the UCF repository.

The older Root Sequence UCF overview remains preserved with its earlier scope notice. Source maps and changelogs retain the interruption-recovery history. The unrecovered 700-case / 561-match progress statement remains excluded from the evidence record; it was not restored as a result.

Research-task status and next review

  • T-001: four editorial cases; no independent reviewer study.

  • T-002: prior synthetic implementation and code/arithmetic checks remain documented; no new field findings.

  • T-003: source-grounded candidate comparison plan now exists; execution remains pending.

  • Author reads section 4 and relevant external passages, then records acceptance, qualification, or rejection of C-003.

  • Author checks the healthcare case and Figure 1B, including what the percentages measure.

  • Review C-001 and C-012, abstract, assistance disclosure, and eventual byline.

  • Choose a bounded T-003 task and check baseline fidelity before evaluation.

  • Continue the wider literature review; do not treat this targeted pass as comprehensive.

No main-branch, site, story-canon, or private-source changes are part of this pass. No other institution's repository was modified.

Root Sequence tests, complicates, and revises the paper—not vice versa.

…d review plan

Add public-safe research scaffold and additive navigation. Preserve existing research and site source. AI-assisted draft; author review pending; no empirical results or deployment.
Connect the dedicated UCF model and synthetic example, reconcile definitions and task statuses, and preserve the older overview. Reran eight implementation tests and the 24-fixture report from verified source. The unrecovered 700-case progress claim is not evidence. Author review pending; no merge or deployment.
@raelovejoy raelovejoy changed the title Start living paper: Coherence Is a Systems Property (v0.1-dev) Living paper v0.1-dev: UCF reconciliation and worked example Sep 16, 2026
…stance record

Add targeted comparisons with STPA, sociotechnical abstraction, values alignment, and full-stack alignment; distinguish published evidence from UCF provenance. Revise C-003 to distinguish interacting technical and normative questions. Add scoped Obermeyer case without claiming replication or deployed benefit. Preserve prior argument, objections, and history. Twenty local structural checks passed; ten uploaded file hashes matched inspected contents. Author review pending; no merge or deployment.
@raelovejoy raelovejoy changed the title Living paper v0.1-dev: UCF reconciliation and worked example Living paper v0.1-dev: external evidence, UCF, and AI disclosure Sep 16, 2026
Add paper-scoped AGENTS guidance and revise AI-ASSISTANCE review checkpoints. Acknowledge conceptual input already contributed without inventing manuscript approval. Preserve verification requirements; no personal health details, research-claim edits, or publication approval.

Copy link
Copy Markdown
Collaborator Author

Question-led collaboration update — 2026-09-16

Commit 9ea2d4bea890e17a71d2cd75de7c068e6d5c9f4d adds paper-scoped AGENTS.md and revises AI-ASSISTANCE.md.

The author requested clarification questions throughout drafting, one manageable passage or decision at a time. Review can use source passages, notes, restatement, and conversational correction; it does not require an unaided defense from memory. Existing conceptual contributions are now distinguished from incomplete review of the current manuscript. Source-verification and independent-evaluation requirements remain unchanged, and no review checkboxes were marked complete.

The change is limited to those two paper-directory files. AI-ASSISTANCE.md contains the dated change record and links to the new instructions. Git comparison confirmed that no research manuscript, claim, code, site, or other file changed in this commit. No empirical tests were run for this documentation-only edit.

No personal health details or private conversation excerpts were added. A personal first-person explanation of AI use is not approved for public attribution by this change. The PR remains a draft; there is no merge, release approval, or deployment.

…g input

Include the combined accessibility/development explanation. Record author intent, tentative terminology, and safeguard proposals under C-003 and C-006 without adopting a new manuscript definition. Add scoped Dekker/STPA source coverage and revision history. No manuscript approval, experiment, implementation, merge, or deployment.

Copy link
Copy Markdown
Collaborator Author

Author-led clarification and combined AI-use explanation — 2026-09-16

Commit 9310de924ff261851992125bc4692472e36fc750 adds the author-requested wording explaining AI as both an accessibility aid and a tool for developing the work to AI-ASSISTANCE.md. This is scoped permission for the explanation, not manuscript/byline approval or permission to disclose medical details.

The author's booking-service input is captured under C-003 (situated reasoning versus coherence) and C-006 (safeguards that expose consequences and support action without defaulting to blame). Author statements, assistant synthesis, candidate terminology, interface suggestions, and unresolved questions are labeled separately. Malconsidered remains tentative. No manuscript or UCF definition was silently replaced.

Added the Dekker 2002 reference with abstract-only coverage and a limited STPA source check of printed pp. 23 and 40, including screenshots. The bibliography now contains nine entries; this is not a new empirical result. Source-map and changelog entries identify the actual reading limits.

Verification: compared this commit with its parent; exactly five existing paper-directory files changed. The claims, source-map, bibliography, and changelog edits are additive. Read back the explanation and the new C-003 discussion from the target branch. No code tests, experimental validation, safeguard implementation, full bibliography rendering, or deployment occurred in this documentation pass.

The next author question concerns a real capacity shortfall after its consequences are visible: whether the process can respond coherently to that constraint while the unmet need remains unresolved. C-003 is still provisional, and no source-review or manuscript-approval checkbox was completed. This PR remains a draft.

Extend Legible Systems with scoped W3C references, sensemaking, supported participation, review burden, and dependency-aware iteration. Add the author's existing-work-first instruction to thought routing and paper guidance. Preserve the active C-003 question without changing the manuscript definition, claims, AI-use explanation, code, or website. Documentation additions; author review remains open.
@raelovejoy raelovejoy changed the title Living paper v0.1-dev: external evidence, UCF, and AI disclosure Living paper v0.1-dev: evidence, author input, and linked practice Sep 17, 2026

Copy link
Copy Markdown
Collaborator Author

Author clarification: personal ASI can participate physically

Context: Continuing the section 4 / C-003 booking-service discussion, with implications for C-009 and the scope of section 8. This is a record of speculative design intent, not evidence of present capability or an adopted manuscript definition.

Author-stated direction: A personal ASI is imagined as a continuing relationship, not a pet or slave and not a direct extrapolation of friendship or AI products as they exist in 2026. The author clarified that friendship is only part of the idea, playfully using “wingbot” for lack of a better term. Ideally it would not be someone's only friend. Its help encompasses both activities it can engage with directly and access to physical infrastructure, including through physical forms. The author's concept therefore does not require choosing between cognitive assistance and physical-world participation.

Assistant correction and proposed implication: The earlier question wrongly separated direct help from physical infrastructure. The fixed-capacity booking fixture remains a limited illustration of allocation under stipulated constraints, not a claim that appointments, institutional bottlenecks, or fixed capacity persist in the imagined setting. Before evaluating an unavoidable shortfall, specify the underlying need and consider whether available intelligence and embodiment can change how it is met, mobilize capacity, or change the infrastructure. These possibilities require explicit scenario assumptions; no guarantee of limitless resources or legitimate authority follows.

Not decided: No exclusive one-ASI-per-person arrangement, body count, mind architecture, universal right to commandeer shared infrastructure, or final relationship label is specified. “Wingbot” remains the author's playful wording, not a new framework or project. Non-ownership remains part of the intended relationship.

Resume: Develop the example with physical participation included rather than re-asking the digital-versus-physical choice. The coherence definition and tests remain open. This comment preserves the clarification; it does not edit the manuscript, UCF model, story canon, or either main branch.

Copy link
Copy Markdown
Collaborator Author

Continuing the personal-ASI example: real-time thought expression

Author input: The author proposes help translating their own thoughts in real time, notes that this might involve cybernetics or neural interfaces, and reiterates changing how a need is met. This is a speculative capability/use case, not a report of using a neural device or an adopted technical architecture.

Assistant interpretation for review: The need can be framed as developing and expressing meaning without first having to package everything into a finished explanation. Distinguish assisted articulation of an intended thought, collaborative development of an unfinished thought, and neural signal decoding. Do not claim these are identical or that an AI interpretation is the person's authentic intent merely because it is fluent. Candidate requirements include easy correction, preserving ambiguity and provenance, and separate permission to express, share, or act on an interpretation.

Examples to explore, not author decisions: Carry a thought across interruptions; move between a developing explanation and a manipulable demonstration; turn a rough design idea into a jointly revised physical prototype through embodiment; or support communication between people without replacing either participant or treating agreement as the objective. These extend the already-recorded cognitive-plus-physical premise, not a new framework.

Existing home checked: concepts/user-configurable-cognitive-interfaces.md, especially personally legible interfaces, stable context, and authority over adaptation. Its present software scope is not evidence for a neural or ASI capability.

Bounded outside reference: Littlejohn and colleagues' 2025 streaming brain-to-voice work is an adjacent example, not evidence of arbitrary thought reading. Berkeley's account quotes the researchers distinguishing attempted-speech production signals from earlier thought/word selection: https://engineering.berkeley.edu/news/2025/03/brain-to-voice-neuroprosthesis-restores-naturalistic-speech/ . The institutional report was inspected; the Nature article could not be opened in this pass. No full-paper review or replication is claimed.

Resume: Use thought expression as an alternative to assuming fixed appointments. Keep the underlying need, means of meeting it, and remaining constraints explicit. No manuscript definition, study result, relationship architecture, or story canon is adopted by this comment.

@raelovejoy

Copy link
Copy Markdown
Collaborator Author

Superseded by draft PR #13. The replacement starts from current main, preserves all 12 files in the coherent-systems paper package from revision 5c15f7f, repairs retired core/ routes, and reconciles the useful cross-domain additions with their current canonical pages.

Closing this older PR without merging prevents its pre-cleanup repository structure from being reintroduced. The paper remains v0.1-dev, AI-assisted, author review pending, and not approved for release. Review continues in #13 at section 4 / C-003; T-003 remains unrun.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant