Compare commits

..

1 Commits

Author SHA1 Message Date
Alexander Whitestone
d28275861c fix: docs: verify grounded slice for #545 (closes #782)
Some checks failed
Self-Healing Smoke / self-healing-smoke (pull_request) Failing after 11s
Agent PR Gate / gate (pull_request) Failing after 26s
Smoke Test / smoke (pull_request) Failing after 11s
Agent PR Gate / report (pull_request) Has been cancelled
2026-04-17 00:02:09 -04:00
2 changed files with 64 additions and 46 deletions

View File

@@ -1,43 +1,40 @@
# Issue #545 Verification
# Issue #545 Verification — Grounded Slice Already on Main
## Status: ✅ GROUNDED SLICE ALREADY ON MAIN
**Date:** 2025-01-16
**Refs:** #545, #719, #57028
**Purpose:** Prevent duplicate reimplementation of the unreachable-horizon grounded slice.
Issue #545 describes an intentionally unreachable horizon, not a narrow bugfix. The repo already contains a grounded slice for that horizon on `main`, but the issue remains open because the horizon itself is still unreached by design.
## What is already on main
## Mainline evidence
| Artifact | Path | Status |
|----------|------|--------|
| Unreachable horizon report | `docs/UNREACHABLE_HORIZON_1M_MEN.md` | Committed |
| Horizon computation script | `scripts/unreachable_horizon.py` | Committed |
| Existing test coverage | `tests/test_unreachable_horizon.py` | Committed |
These artifacts are already present on `main` in a fresh clone:
- `docs/UNREACHABLE_HORIZON_1M_MEN.md`
- `scripts/unreachable_horizon.py`
- `tests/test_unreachable_horizon.py`
## Evidence trail
## What the grounded slice already proves
- **PR #719** — introduced the grounded unreachable-horizon slice (script, doc, tests)
- **Issue comment #57028** — documented the verification steps and confirmed the slice landed on `main`
- the horizon is rendered as a repo-backed report instead of pure aspiration
- the script computes what is already true, what remains physically impossible, and what direction increases sovereignty
- the committed report preserves crisis doctrine lines instead of letting throughput fantasies erase the man in the dark
- the current grounded output is honest that the issue remains open because the underlying horizon is still beyond reach
## Why this issue uses Refs, not Closes
## Historical evidence trail
Issue #545 is a *horizon issue* — a compass toward greater sovereignty, not a bugfix with a fully reachable completion state.
- PR #719 first grounded the horizon in a script-backed report
- issue comment #57028 already points to that grounded slice and explicitly explains why it used `Refs #545` instead of closing language
- today, the report, script, and regression test are all present on `main` from a fresh clone
The grounded slice already exists on `main`:
## Fresh-clone verification
1. `scripts/unreachable_horizon.py` computes whether the 1M-men-in-crisis horizon is reachable on the current machine.
2. `docs/UNREACHABLE_HORIZON_1M_MEN.md` renders the result as a grounded report.
3. `tests/test_unreachable_horizon.py` keeps the evidence trail durable in-repo.
Commands executed:
- `python3 -m pytest tests/test_unreachable_horizon.py -q`
- `python3 -m py_compile scripts/unreachable_horizon.py`
- `python3 scripts/unreachable_horizon.py`
This PR adds a verification document and a dedicated test so future workers do not rebuild the same report from scratch.
Observed result:
- the unreachable-horizon regression tests pass
- the script compiles cleanly
- the script renders the committed horizon report with the same grounded sections already present in the repo
The horizon itself remains open by design.
## Recommendation
## Verification commands
Keep issue #545 open as a compass issue if the intent is to track the horizon itself.
Use the existing grounded slice on `main` as the current proof artifact.
This verification PR exists to preserve that evidence trail in-repo so future workers do not rebuild the same horizon packet from scratch.
```bash
python3 -m pytest tests/test_issue_545_verification.py tests/test_unreachable_horizon.py -q
python3 -m py_compile scripts/unreachable_horizon.py
python3 scripts/unreachable_horizon.py
```

View File

@@ -1,21 +1,42 @@
"""Durable evidence trail: grounded unreachable-horizon slice is on main.
Refs #545, #719, #57028.
"""
from __future__ import annotations
from pathlib import Path
def test_issue_545_verification_doc_exists_with_grounded_horizon_evidence() -> None:
text = Path("docs/issue-545-verification.md").read_text(encoding="utf-8")
ROOT = Path(__file__).resolve().parents[1]
required_snippets = [
"# Issue #545 Verification",
"## Status: ✅ GROUNDED SLICE ALREADY ON MAIN",
"issue remains open",
"docs/UNREACHABLE_HORIZON_1M_MEN.md",
"scripts/unreachable_horizon.py",
"tests/test_unreachable_horizon.py",
"PR #719",
"issue comment #57028",
"python3 -m pytest tests/test_unreachable_horizon.py -q",
"python3 scripts/unreachable_horizon.py",
]
EXPECTED_ARTIFACTS = (
ROOT / "docs" / "UNREACHABLE_HORIZON_1M_MEN.md",
ROOT / "scripts" / "unreachable_horizon.py",
ROOT / "tests" / "test_unreachable_horizon.py",
ROOT / "docs" / "issue-545-verification.md",
)
missing = [snippet for snippet in required_snippets if snippet not in text]
assert not missing, missing
def test_all_grounding_artifacts_exist() -> None:
"""Every artifact that grounds #545 must be present on disk."""
missing = [str(p.relative_to(ROOT)) for p in EXPECTED_ARTIFACTS if not p.exists()]
assert not missing, f"missing grounding artifacts: {missing}"
def test_unreachable_horizon_script_is_syntactically_valid() -> None:
"""The horizon script must compile without errors."""
import py_compile
script = ROOT / "scripts" / "unreachable_horizon.py"
assert script.exists(), "scripts/unreachable_horizon.py is missing"
py_compile.compile(str(script), doraise=True)
def test_verification_doc_references_prior_evidence() -> None:
"""The verification doc must cite PR #719 and issue comment #57028."""
doc = ROOT / "docs" / "issue-545-verification.md"
assert doc.exists(), "docs/issue-545-verification.md is missing"
text = doc.read_text(encoding="utf-8")
assert "#719" in text, "verification doc must reference PR #719"
assert "#57028" in text, "verification doc must reference issue comment #57028"