Skip to content

docs: make Method Factory README reader-first - #4

Merged
RedEyeNinja-BKK merged 2 commits into
mainfrom
docs/readme-audience-ux
Aug 8, 2026
Merged

docs: make Method Factory README reader-first#4
RedEyeNinja-BKK merged 2 commits into
mainfrom
docs/readme-audience-ux

Conversation

@RedEyeNinja-BKK

Copy link
Copy Markdown
Owner

Docs-only: reader-first README for Method Factory

README Audience-UX revision. README.md only - no product code, tests, CI, package version (2.0.0rc1), ADRs, or release objects changed.

What changed

Rewrote README.md with a reader-first information architecture, using the Process Engine README as a reader-experience reference (not copied wording):

  1. Outcome-oriented hero - answers "what does this do for me?" before any storage/implementation detail.
  2. Plain-language "What it does" - the human journey (1-8) alongside the pipeline diagram.
  3. "Why Method Factory?" - the code-enforces / model-creates / human-gates insight without requiring Action Envelope knowledge.
  4. "What makes it different" - benefit language first.
  5. "Who this is for" - good fit / not a fit, transparent about RC limitations.
  6. "What using it feels like" - a concrete Etsy-store agent-package walkthrough.
  7. "What RC1 provides today" - explicit distinction between the product architecture and the packaged public surface (mf migrate-store + mf export only; lifecycle/import/backup/restore/GC not exposed).
  8. Engineering detail moved downward - validation, architecture, and the hash-chain non-claim condensed and linked out.

Base: 380b8e376e0b1ecac1443ef2c9ee104268236a70 (current main). Release identity v2.0.0-rc.1 untouched.

README Audience-UX revision (docs-only). Rewrites README.md with a
reader-first information architecture modeled on the Process Engine
README's reader experience (not its wording):

- outcome-oriented hero answering 'what does this do for me' before any
  storage/implementation detail;
- plain-language 'What it does' with the human journey alongside the
  pipeline diagram;
- 'Why Method Factory?' explaining the code-enforces / model-creates /
  human-gates insight without requiring Action Envelope knowledge;
- 'What makes it different' in benefit terms;
- 'Who this is for' (good fit / not a fit) with transparent RC
  limitations;
- 'What using Method Factory feels like' - a concrete Etsy-store example
  walkthrough;
- 'What RC1 provides today' - explicit distinction between the product
  architecture and the packaged public surface (migrate-store + export
  only; lifecycle not exposed; no import/backup/restore/GC);
- engineering detail (validation, architecture, hash-chain non-claim)
  moved downward and condensed;
- Process Engine presented as lineage, not dependency.

Only README.md changed. Product code, tests, CI, package version
(2.0.0rc1), ADRs, and release objects untouched.
README-only follow-up on docs/readme-audience-ux (PR #4):

1. Fix broken Process Engine case-study link: evals/case-study-first-run.md
   (404) -> case-study/case-study-first-run.md (canonical live path,
   verified 200 via GitHub API). External GitHub file links now verified,
   not just internal paths.
2. Surface the RC1 usability boundary near the top: concise callout after
   the plain-language opening notes the deterministic foundation is real,
   v2.0.0-rc.1 is an engineering RC, the packaged public interface exposes
   migrate-store/export, and the full conversational authoring lifecycle
   is not yet a polished public entry point. No duplication of the full
   'What RC1 provides today' section.
3. Improve Getting Started installation UX: explicit download-from-GitHub-
   Release step before pip install of the local wheel; editable install
   clearly marked as the development/contributor path, not equivalent to
   public release installation. No PyPI instructions (RC1 is not on PyPI).

Release artifact boundary respected: v2.0.0-rc.1 tag/release/wheel
untouched; no wheel rebuilt or asset replaced; no claim that a wheel from
this docs branch is the released artifact.

README.md only; product code/tests/CI/package version unchanged.
@RedEyeNinja-BKK
RedEyeNinja-BKK merged commit abaf09b into main Aug 8, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant