Files
lanework/strategy/README.md
T
rzen 4c179f63fc The plan closes its own loop — executed 2026-08-08, steps 1 through 8, each committed green
Step 8's verification record: 2,707 unit tests green at close (the golden fixture suite among them, untouched — no git fixtures ever existed); the UI test targets compile; the keeper behaviors — a board beside a real .git opened, watched, and healed byte-identically — are pinned by GitAgnosticStorageTests, FolderWatcherTests, and the gitignore/relocation suites, all green. The accessibility audit could not run to a verdict in this environment (its AX sweep flagged another app's fullscreen video element — the same failure on surfaces the excision never touched); the popover audit's own screenshot shows the strip as ruled: Info, Theme, Sync.

Claude-Session: https://claude.ai/code/session_014PtZdPwqZuqEDLc6wZMtEy
2026-08-08 12:43:25 -04:00

16 lines
1.3 KiB
Markdown

# Release & Distribution Strategy
Long-term strategy work for Lanework's release, distribution, and business model: licensing, monetization, openness, marketing, and goals. Sibling to `research/` (the competitive-landscape corpus, which this directory draws on) but different in kind — `research/` gathers evidence about the market; `strategy/` turns evidence into positions, decisions, and plans for Lanework specifically.
## Documents
- [00-charter.md](00-charter.md) — the framing document: strategic goal, the two tier anchors, what is already ruled, the decision surface, the tensions to resolve, and the research agenda (start here)
- [01-git-excision.md](01-git-excision.md) — **ruled and executed 2026-08-08** — the plan for removing app-managed git entirely: keepers, harvest, delete list, sequencing, deferred successors; the stack is out, resurrection point at tag `pre-git-excision`
Workstream documents are added as they happen, numbered in sequence.
## Conventions
- Same conventions as `research/`: each document opens with a scope note and a dated line; prose is unwrapped — one line per paragraph or list item.
- A **position** is a working stance open to revision; a **ruling** is a decision recorded in DESIGN/ or RELEASE.md and stands unless explicitly re-ruled. Strategy documents may propose re-rulings but never silently contradict one.