docs(field-log): revised prose for the revitalization log - #5
Draft
mparrett wants to merge 1 commit into
Draft
Conversation
Reworks the log's framing throughout. The version you merged was written from outside and reads that way in places — 'the repo we inherited', 'the agent's machinery', 'provenance, not garbage'. This rewrites those toward what was actually true: a solo project with its own process layer, joined by someone who could not see it yet. Both of your corrections are preserved verbatim, including the ITER-0005 caveat. Adds a §7 note naming the original claim and why it was wrong, and a paragraph crediting you for the corrections. Retitled 'Opening the Door'. Filename, source links, and cross-links all target this repo; nothing here points at the fork.
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.
Draft, so there's something concrete to react to rather than a rendered link. Part of #4 (row 5) — merge, comment, or close.
What this is
I kept revising this log after you'd merged it, so the two copies drifted. This brings the revised prose over top of your corrections, ending the divergence.
The rewrite is about stance. I wrote the original before I understood the process layer, and it shows: "the repo we inherited", "the agent's machinery", "the harness is provenance, not garbage". That reads like I'd found something abandoned. What was actually there was a solo project with a working process layer I hadn't looked at yet.
A few examples:
§1 What the machine left behind→What a fresh clone metYour corrections
Both from #1 (merged as 137d449) are preserved verbatim, including the ITER-0005 caveat. Wanted to be careful not to silently revert your edits — verified.
Two additions: a §7 note that quotes the previously incorrect "never had a reviewer" claim, and a paragraph crediting you for the corrections.
Notes
fmpl-tour.html,fmpl-field-log.html) point at this repo; nothing references my fork.