docs: soul-file ISSUES-INDEX + HB-003 github-settings drift#83
Merged
AceHack merged 4 commits intoLucent-Financial-Group:mainfrom Apr 22, 2026
Merged
Conversation
…inancial-Group#55-82 for soul-file independence Aaron 2026-04-21: *"oh yeah remember we are git native so still keep a record in the soul file for independence"* — after 28 BACKLOG rows translated to LFG GitHub issues (Lucent-Financial-Group#55-Lucent-Financial-Group#82) via parallel agent dispatch, the soul-file (git repo) must independently retain the record so the factory is reproducible without GitHub. Index maps each issue number to: - priority (P0/P1) - title - BACKLOG.md source section + line-range - GitHub URL (LFG remote) Authoritative content stays in docs/BACKLOG.md; GitHub issues are a dispatch surface, not the record of truth. If GitHub or the LFG org vanishes, a fork can reconstitute the tracker from this file + BACKLOG.md via the documented regeneration protocol. Composes with: - memory/user_git_repo_is_factory_soul_file_reproducibility_substrate_aaron_2026_04_21.md - memory/feedback_capture_everything_including_failure_aspirational_honesty.md - memory/feedback_witnessable_self_directed_evolution_factory_as_public_artifact.md Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
…erence) Cross-reference BACKLOG.md ↔ ISSUES-INDEX.md so a future contributor reading BACKLOG discovers the issue-tracker mapping without needing to know the file name already. Retractable-safe additive edit (one bullet in Meta section, no row content modified). Composes with the ISSUES-INDEX.md landing in d6ded51. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Autonomous drift-check tick on LFG/Zeta surfaced a single-line bounded diff: `build-and-test (macos-14)` is in checked-in expected snapshot but absent from live branch-protection. Matches prior task Lucent-Financial-Group#191 decision (macOS on AceHack fork, Linux on LFG). Agent declined to overwrite the baseline autonomously — shared-infra policy moves want explicit human sign-off so unrelated drift isn't silently ratified. Row files the decision for Aaron. Fighter-pilot discipline: tactical authority on retractable reads (run drift-check), chain-of-command preserved on policy writes (baseline update). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Adds a git-native “soul-file” index that maps GitHub issues back to their originating docs/BACKLOG.md rows, and records a GitHub settings-drift decision for human disposition—aiming to keep the factory reconstructible from git alone.
Changes:
- Introduces
docs/ISSUES-INDEX.mdto map LFG GitHub issues (#55–#82) back todocs/BACKLOG.mdsections + line ranges. - Adds a
docs/BACKLOG.mdmeta pointer to the new issues index for discoverability. - Adds HB-002 / HB-003 entries to
docs/HUMAN-BACKLOG.md(including the GitHub-settings drift disposition decision).
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 6 comments.
| File | Description |
|---|---|
| docs/ISSUES-INDEX.md | New index file mapping GitHub issues to BACKLOG line ranges + reconstruction protocol. |
| docs/HUMAN-BACKLOG.md | Adds human-decision backlog rows HB-002 and HB-003 (incl. GitHub settings drift disposition). |
| docs/BACKLOG.md | Adds a meta bullet pointing to docs/ISSUES-INDEX.md as the git-native cross-index. |
…fixes ISSUES-INDEX.md (P0 + three P1 Copilot comments): - Replace brittle line-range anchors with section-header + bullet-keyword anchors. Line numbers drift on every BACKLOG edit; section titles and bold-title keywords survive. All 28 row anchors verified to resolve to their sections on this PR branch. - Drop auto-memory cross-references (files under `memory/*` that live outside the git tree and therefore violate the "standalone reconstruction from this repo" soul-file discipline the doc is defending). - Replace contributor-name prose filename reference with role-neutral language per `docs/AGENT-BEST-PRACTICES.md` L284-L290 (names confined to `memory/persona/<name>/` and optionally `docs/BACKLOG.md`). - Add a Source-availability note for six rows whose source bullets are expected to land via Batch 6 of the speculative drain (Lucent-Financial-Group#57, Lucent-Financial-Group#60, Lucent-Financial-Group#63, Lucent-Financial-Group#79, Lucent-Financial-Group#80, Lucent-Financial-Group#81); mark them `source pending Batch 6 drain` so re-verification after the drain is explicit. - Expand the What-this-file-is-NOT and Composition sections to cite in-tree authoritative sources (BACKLOG.md, GOVERNANCE.md §2/§24, HUMAN-BACKLOG.md) instead of auto-memory paths. HUMAN-BACKLOG.md (two Copilot comments): - HB-002: decisions file path was cited as if present, but the ADR was drafted on the speculative fork branch and lands on LFG only via Batch 6. Rephrase the Source cell to describe current location + expected on-LFG path, so the citation stays valid before and after the drain. - HB-003: replace the "in-flight Round 44 notes" pointer (no in-repo path) with the concrete commit `77c2450` (`gate.yml: split macOS leg to forks only; drop (macos-14) from LFG required checks`) which implemented the matrix split that produced this drift. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Member
Author
|
Addressed all 6 Copilot review comments in commit ISSUES-INDEX.md:
HUMAN-BACKLOG.md:
Added a Source-availability note covering the six rows (#57, #60, #63, #79, #80, #81) whose bullet keywords expect to resolve only after Batch 6 drain — those are explicitly marked Threads resolved. Re-arming auto-merge. |
AceHack
added a commit
that referenced
this pull request
Apr 22, 2026
Three P1 Copilot findings on this org-transfer cleanup PR, addressed in-place per the drain-pre-check discipline (captured in auto-memory after PR #83 rework cycle): 1. docs/security/INCIDENT-PLAYBOOK.md:369-370 — the contact-tree primary line carried a contributor name ("Aaron") and a mid-repo-identifier line wrap. Rewrote to role-neutral ("human maintainer") with the repo identifier held as a single inline token. 2. .claude/skills/nuget-publishing-expert/SKILL.md:30-31 — stale operational-state line said the repo was private on AceHack; the whole point of this PR is to reflect the Lucent-Financial-Group/Zeta transfer and public-visibility flip. Updated to match current state and note the remaining NuGet gates (prefix-reservation + release.yml) so the skill stays internally consistent. Also merged origin/main into this branch to clear the BEHIND status left by PR #83's landing. No other file changes; PR scope remains the four URL cleanups Copilot otherwise rated clean.
3 tasks
AceHack
added a commit
that referenced
this pull request
Apr 22, 2026
…p/Zeta (#48) * cleanup: update 4 outdated AceHack/Zeta URLs to Lucent-Financial-Group/Zeta Post-transfer operational-state references that weren't caught in the initial transfer pass. All four are current-state statements (API endpoint examples, package metadata, maintainer-contact info) that read as current truth — not historical records of actions taken on the old repo. Files + change shape: - `.claude/skills/nuget-publishing-expert/SKILL.md` — `<PackageProjectUrl>` + `<RepositoryUrl>` in the NuGet metadata example; plus `<Company>AceHack</Company>` → `Lucent Financial Group`. The skill documents what gets published on `dotnet pack`, which now ships under the LFG identity. - `docs/copilot-wins.md` — the `gh api repos/…/pulls/…/comments` example uses the real current-state repo path so contributors can copy-paste it. - `docs/NAMING.md` — naming sheet row that was literally parenthesised "currently `AceHack/Zeta`"; now `Lucent-Financial- Group/Zeta`. The "currently" hedge is gone; LFG is the steady state. - `docs/security/INCIDENT-PLAYBOOK.md` — contact tree. Incident responders reading the playbook need the current canonical repo identifier, not the pre-transfer one. Explicitly NOT touched: - `docs/ROUND-HISTORY.md`, `docs/HUMAN-BACKLOG.md`, `docs/GITHUB-SETTINGS.md`, `docs/FACTORY-HYGIENE.md`, `docs/research/parallel-worktree-safety-2026-04-22.md`, `docs/HARNESS-SURFACES.md` — these carry AceHack/Zeta refs as *historical record* (transfer-event narration, empirical-test results literally run on the pre-transfer repo, FACTORY-HYGIENE row describing the triggering incident). Docs-read-as-current- state rule (GOVERNANCE §2) doesn't touch the archive layer, and round-history + ADR-style records of *what happened where* are that archive layer. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * address Copilot P1 findings on PR #48 Three P1 Copilot findings on this org-transfer cleanup PR, addressed in-place per the drain-pre-check discipline (captured in auto-memory after PR #83 rework cycle): 1. docs/security/INCIDENT-PLAYBOOK.md:369-370 — the contact-tree primary line carried a contributor name ("Aaron") and a mid-repo-identifier line wrap. Rewrote to role-neutral ("human maintainer") with the repo identifier held as a single inline token. 2. .claude/skills/nuget-publishing-expert/SKILL.md:30-31 — stale operational-state line said the repo was private on AceHack; the whole point of this PR is to reflect the Lucent-Financial-Group/Zeta transfer and public-visibility flip. Updated to match current state and note the remaining NuGet gates (prefix-reservation + release.yml) so the skill stays internally consistent. Also merged origin/main into this branch to clear the BEHIND status left by PR #83's landing. No other file changes; PR scope remains the four URL cleanups Copilot otherwise rated clean. --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Three net-new soul-file commits landing on LFG, per Aaron 2026-04-21 directive: "we are git native so still keep a record in the soul file for independence" — the git repo itself must independently retain the record of what got translated to GitHub issues, so the factory remains reproducible from git alone.
fd2125f— landdocs/ISSUES-INDEX.md: git-native mapping of LFG issues <P0> Nation-state + supply-chain threat-model rewrite #55-<P1> Escalate-to-human-maintainer criteria-sweep (will-propagation gap) #82 back to their BACKLOG.md source rows (section + line range). Authoritative-pointer, not authoritative-content: BACKLOG stays the source of truth; the index is a cross-reference that survives any GitHub issue-tracker outage or migration.604785e— BACKLOG.md meta-section pointer to ISSUES-INDEX.md so the cross-reference is discoverable from the authoritative record.0c9cca9— HUMAN-BACKLOG.md HB-003 row: a drift-check autonomous pass foundtools/hygiene/github-settings.expected.jsonhasbuild-and-test (macos-14)in the checked-in baseline but absent from live LFG branch-protection (matches prior task frontier-readiness: gap #5 audit — 3 directory-level audits (agents + openspec + github) #191 build-matrix-split decision). Agent declined to auto-update the baseline on a retractable-safe tick (shared-infra-policy; baseline updates want human sign-off so unrelated drift isn't silently ratified) — surfaces the decision for Aaron rather than silently waiting.Why this is the right shape
cp ... expected.json) → course-correction (file the row instead). Preserved in git history legibly.Test plan
docs/ISSUES-INDEX.mdissue→line mappings resolve against currentdocs/BACKLOG.mdline numbersbash tools/hygiene/check-github-settings-drift.shstill exits 1 with the same single-line diff (no baseline mutation in this PR)🤖 Generated with Claude Code