Files
poli0981andClaude Opus 5 81011315ab feat(tier2): PresentMon is dropped, and Tier 2 keeps its place while losing its mechanism (#96)
Owner decision 2026-08-27. §S31 retired PresentMon as a measurement ORACLE (row
P2); this removes it as an IMPLEMENTATION. It is not bundled, not fetched, not
used, and tools/frametype-oracle.ps1 -- the parser written for its output -- is
deleted with it, along with its build.ps1 gate.

THE DISTINCTION THIS COMMIT IS BUILT ON: dropping PresentMon is not dropping
Tier 2. The owner's earlier instruction was explicit that a release "will use a
different approach", so Tier 2 keeps its place in the design and loses its named
tool. Nothing here rewrites the tier out of the product; everything here stops
naming an implementation nobody chose.

TWELVE DOCUMENTS NAMED IT AS THE MECHANISM AND EVERY ONE IS CORRECTED:
CLAUDE.md's pinned-stack row; README's capture-tier table AND its safety row;
01_ARCHITECTURE's tier table and ADR-3; 03_METRICS rung 2; 04_CAPTURE's source
table and tier selection; 05_DETECTION's two Tier-2 rows; 07_IPC's
PresentMonMissing error code; 12_BUILD; 14_TESTING's CSV-parser row;
15_ROADMAP's P2 phase and v2 backlog; and legal/THIRD_PARTY_NOTICES.md plus
legal/licenses/README.md. Struck in place rather than deleted wherever the
reasoning is what a later reader needs.

THE NOTICES ROW AND license-check's CLAIM HAD TO GO TOGETHER, AND THAT IS THE
GATE WORKING. tools/license-check.ps1 bound `Intel PresentMon` to
assets/native/PresentMon.exe BIDIRECTIONALLY, so removing the row alone fails
with "no table row mentions Intel PresentMon, so its bundling claim cannot be
checked". Removing a claim is a deliberate act and is recorded as one, in the
notices file itself. legal/licenses/README.md also listed a presentmon-MIT.txt
that never existed -- a row pointing at a file nobody had shipped.

§M1, §M2 AND §M6 CLOSE BY DECISION, NOT BY MEASUREMENT, and each row says which.
They were questions about a tool that no longer has a subject. §M2's answers are
kept in full -- the binary's identity, its refusal to run unelevated, the 24-column
set -- because every one of them cost a measurement, and a closed row that deletes
its evidence is how the next person re-runs it.

§G IS NOT CLOSED. IT GETS BIGGER. "Is the binary committed or fetched?" becomes
"by what mechanism does a shipped build reach Tier 2 at all?", and nothing in
this repository names one. The row now carries its own constraints: README's
capture-tier table and its SAFETY row, legal/DISCLAIMER.md §73 and
legal/EULA.md §33 all describe a no-injection mode as THE DEFAULT for uncertain
cases; ETW needs elevation regardless of tool (§M6); and 15_ROADMAP has no v2
fallback any more either.

WHAT THIS COSTS USERS, PUT WHERE THEY WILL READ IT. README's safety row promised
"always a way out". It now carries, in that row, that the mode is unbuilt and has
no chosen mechanism, and that A REFUSED OR UNHOOKABLE TITLE GETS TIER 3 --
session duration and hardware telemetry. Said in the safety table rather than in
a footnote, because a way out that does not exist is the wrong thing to be
reassured by.

THE TWO LEGAL DOCUMENTS ARE DELIBERATELY NOT TOUCHED. DISCLAIMER §73 and EULA §33
still call the no-injection mode "the default" without the qualification the
README now carries. That is a real gap, §G names both files, and changing a legal
document is not a cleanup -- it is an owner decision with its own review.

AND THE DISCRIMINATOR RUN PRODUCED NOTHING, so it settled nothing. The command I
supplied targeted explorer.exe, which may present nothing PresentMon tracks, so
"no CSV" and "no FrameType column" are indistinguishable -- the §Traps entry
about a canary that dies before reaching the gate, in a command I wrote. A target
known to present would have settled it. Recorded in §S31 and spike-notes §11 so
nobody re-runs it believing it is untried, and moot either way now.

Also corrected while in the file: CLAUDE.md's tools list omitted
hookinventory-check. Same class as §R10 and found by counting the directory
rather than by reading the line.

./build.ps1 check with no switches: PASSED, one skipped gate (resx-audit, which
does not exist). license-check green -- the row/claim pair was removed
consistently, which is the only way that gate can stay green.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>


---

docs: two pointers to a script that was never landed, left by closing #94

`spike-notes` §11 and `HANDOFF` item 3 both credited the §S31 run to
`tools/s31-capture.ps1`. That script lived in #94, which was closed unmerged
because it drives PresentMon and PresentMon was dropped the same day. So two
documents on `main` name a file the repository does not contain -- a reader
follows the pointer and finds nothing.

Caught by grepping `main` for the name after the close, not by reading the
diff: the reference was correct when it was written and became wrong when a
DIFFERENT pull request was closed. That is the "a document can go stale by NOT
being touched" entry arriving from the one direction §Traps does not describe --
staleness caused by a decision taken elsewhere.

Both now describe the run without naming an artifact, and `spike-notes` says
explicitly that the script is not in this repository so nobody goes looking.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-28 09:57:36 +07:00

130 lines
3.7 KiB
Plaintext

# ---------------------------------------------------------------------------
# FrameLedger — repository ignore rules
# ---------------------------------------------------------------------------
# --- .NET / MSBuild --------------------------------------------------------
[Bb]in/
[Oo]bj/
# The rule fixture corpus is DATA, not build output, and some of it has to be
# named after the thing it imitates. `tests/fixtures/rules/engines/source/bin/`
# mirrors a real Source layout, and `[Bb]in/` above silently swallowed it: the
# file existed on the machine that wrote it, so the fixture passed locally and
# failed on a fresh clone with "engine: null". `git add -A` reported nothing,
# because an ignored file is not an untracked one.
#
# Negations must come after the pattern they undo, and the parent directory has
# to be re-included first or git never descends into it.
!tests/fixtures/rules/**/bin/
!tests/fixtures/rules/**/bin/**
[Dd]ebug/
[Rr]elease/
[Xx]64/
[Ll]og/
[Ll]ogs/
*.user
*.suo
*.userosscache
*.sln.docstates
*.binlog
*.nupkg
*.snupkg
project.lock.json
project.fragment.lock.json
artifacts/
out/
TestResults/
BenchmarkDotNet.Artifacts/
coverage*.json
coverage*.xml
coverage*.info
*.coverage
*.coveragexml
# --- Native / CMake / MSVC -------------------------------------------------
build/
[Bb]uild[0-9]*/
cmake-build-*/
CMakeFiles/
CMakeCache.txt
CMakeUserPresets.json
cmake_install.cmake
compile_commands.json
*.dir/
*.obj
*.pdb
*.ilk
*.exp
*.idb
*.tlog
*.ipch
*.aps
*.ncb
*.opendb
*.opensdf
*.sdf
*.VC.db
*.VC.opendb
ipch/
.vs/
Testing/
# --- Vendored third-party sources (fetched, not committed) -----------------
# NVAPI headers + import lib ARE committed (12_BUILD.md §NVAPI SDK).
# MinHook is a submodule / FetchContent — its build output is not.
src/native/third_party/**/build/
_deps/
# NOTE: there are no bundled native assets. assets/native/PresentMon.exe was the
# only one ever planned and PresentMon was DROPPED on 2026-08-27 (S31 row P2,
# then an owner decision). The path is left unignored anyway: if a future Tier-2
# mechanism ever needs a bundled binary there, an ignore rule is how it would be
# missed rather than reviewed.
# /presentmon/ IS ignored, and it is NOT the path above. A hand-downloaded copy
# of the Intel console binary landed at the repository root on 2026-08-27 --
# staged for the §S31 run -- untracked and matched by no rule, so `git add -A`
# would have committed a 956 KB third-party executable at a path no document
# names, outside legal/THIRD_PARTY_NOTICES.md and carrying no VERSIONINFO.
#
# This is not the mistake the note above warns about. That note is about
# ignoring the CANONICAL path; this ignores a scratch one. The canonical path
# stays unignored, and it stays empty: the owner decided on 2026-08-27 that the
# console binary is a LOCAL TEST TOOL -- not committed, not fetched, not
# redistributed -- and that a release reaches Tier 2 some other way
# (docs/20_OPEN_QUESTIONS.md §G). The canonical path is left unignored anyway,
# because that decision can be revisited and an ignore rule is how it would be
# revisited by accident.
/presentmon/
# --- Velopack / packaging --------------------------------------------------
Releases/
packages/
*.vpk
# --- Tooling / editors -----------------------------------------------------
.idea/
.vscode/
!.vscode/extensions.json
*.swp
*~
# --- OS --------------------------------------------------------------------
[Tt]humbs.db
ehthumbs.db
Desktop.ini
$RECYCLE.BIN/
.DS_Store
# --- Local-only ------------------------------------------------------------
# Never commit captured game data, real session databases, or crash dumps.
*.db
*.db-wal
*.db-shm
*.dmp
local/
scratch/
# Claude Code worktrees live inside the repo but are separate checkouts.
.claude/worktrees/