wushenghua/aetherbound-guild
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: activate DEV-3 guild and market plan

Browse Source
This commit is contained in:
wushenghua
2026-08-18 00:36:09 +08:00
parent ec9a83e8bb
commit 60c2c566ea
2 changed files with 97 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CURRENT_CHECKPOINT.md
+13 -7
View File
@@ -13,8 +13,8 @@
## Current State
- Stage: `DEV-2_INITIAL_COMPANY_COMPLETE`
- Active implementation step: `NONE_DEV-3_PENDING_ACTIVATION`
- Stage: `DEV-3_GUILD_FIRST_MARKET_IN_PROGRESS`
- Active implementation step: `DEV-3A_CONTRACT_FOUNDATION`
- Planning baseline: `d59555c5a3cf95fc44de79ba06c02e650eb3df3b`
- Documentation consolidation baseline:
`53824d2394e7facdc8dca19aa20a690a5c960aca`
@@ -180,6 +180,11 @@
and the preserved FG-4 regression at
`/private/tmp/aetherbound-guild-test-evidence/dev2-final-fg4-regression/20260817T155717Z-30828`,
both with strict diagnostics 0 and complete runner cleanup. DEV-2 is complete.
- DEV-3 is activated under one durable five-substep plan. DEV-3A owns only the
authoritative Company-store migration and deterministic first Contract/
Market persistence: v1 Company compatibility, one active Contract, 52 Coin,
Line capacity four, exact 3/4/3 offers and retry-safe receipts. Guild UI,
Market review and hiring remain later DEV-3 substeps.
- Broader human comprehension/fun, device, package and release gates remain
`OPEN`.
@@ -194,7 +199,7 @@
## Frozen
- Runtime changes outside `DEV-2`.
- Runtime changes outside active `DEV-3A`.
- Pixel asset expansion.
- FG-5 and later Regions.
- New image generation during planning review.
@@ -203,7 +208,8 @@
## Next Action
Create and push the DEV-2 closure record, verify HEAD equals upstream and the
worktree is clean, then activate one durable `DEV-3` Guild and first Market
plan before changing product code. DEV-4 through DEV-6 remain pending and must
advance one focused pushed step at a time.
Implement and narrowly verify `DEV-3A`: migrate the verified Company store into
one authoritative Contract/Market state without changing its two Recruit
records, create exactly one retry-safe first Contract with 52 Coin, Line
capacity four and a stable 3/4/3 board, then push the focused boundary before
activating Guild UI work.
docs/06_DEVELOPMENT_AND_REVIEW.md
+84 -7
View File
@@ -424,18 +424,17 @@ signing, device installation, stores and publishing remain outside this plan.
### Immediate Next Action
Push the verified DEV-2 closure record, confirm HEAD equals upstream and the
worktree is clean, then activate exactly one durable DEV-3 Guild and first
Market plan. Do not change DEV-3 product code until that activation commit is
pushed; DEV-4 through DEV-6 remain pending and advance only after each earlier
step reaches its focused pushed boundary.
Implement `DEV-3A` as the first bounded Guild/Contract persistence change.
Preserve the verified Initial Company and its two stable Recruit records while
adding one authoritative, migrated Contract/Market state; DEV-3B and later
remain frozen until DEV-3A passes its focused checks and is pushed.
<!-- Historical section source: IMPLEMENTATION_PLAN; retained in Git history. -->
## FG-4 Japanese 2D Hand-Drawn Redevelopment Plan
> Status: `OWNER_APPROVED`
> Active implementation step: `NONE_DEV-3_PENDING_ACTIVATION`
> Active implementation step: `DEV-3A_CONTRACT_FOUNDATION`
> Goal: `06_DEVELOPMENT_AND_REVIEW.md`
> Contract: `06_DEVELOPMENT_AND_REVIEW.md`
> Page plan: `03_PAGES_AND_UX.md`
@@ -449,7 +448,7 @@ step reaches its focused pushed boundary.
| `DEV-0` Planning and cleanup | `COMPLETE` | Six current documents define the game, pages, art direction and order. | Owner approved entry-first development. |
| `DEV-1` Boot, first launch and Title | `READY` | Launch, verification, language/accessibility setup, Title and essential Settings form one working game entry in the accepted Japanese 2D fantasy UI language. | Owner can reopen, reset, change settings and reach New Game without dead controls, and accepts the play-size visual result. |
| `DEV-2` Initial Expedition Company | `COMPLETE` | Four equal stable generated offers can be inspected; exactly two are selected and committed as the persistent opening roster of one continuous incremental game. | Owner accepted candidate v3 for continuation; source-bound DEV-2 and preserved FG-4 suites pass at source `4352e25`. |
| `DEV-3` Guild and first Market | `PENDING` | The Guild identifies the next action; Market comparison and recruit review build the opening Company. | Every purchase, cancel, affordability and return path is truthful. |
| `DEV-3` Guild and first Market | `IN_PROGRESS` | The Guild identifies the next action; Market comparison and recruit review build the opening Company. | Every purchase, cancel, affordability and return path is truthful. |
| `DEV-4` Automatic formation and risk | `PENDING` | Player chooses members; the system orders them and exposes protection, reach, threat and reward before commitment. | Owner can explain the formation and selected risk without coaching. |
| `DEV-5` Battle, result and recovery | `PENDING` | Real melee, ranged, magic, healing, guard, damage, knockout, reward and next-stage recovery complete the first 15-20 minute loop. | Owner completes one full first cycle in a playable H5 and sees the same knocked-out Recruit return next stage. |
| `DEV-6` Second cycle and Company management | `PENDING` | Persistent roster, equipment, Artifacts, levels, promotion, Save/resume, dismissal and Contract return support continued play. | Owner understands retained growth, battle-local knockout and the next decision. |
@@ -636,6 +635,69 @@ before it is sent for review. A later repair does not erase an earlier rule.
ledger before the next candidate. `human_reviewed` remains false until the
Owner explicitly accepts the current runtime revision.
### DEV-3 Durable Implementation Plan
Player-visible stopping point:
```text
launch and Continue the persistent two-Recruit Expedition Company
-> see the Guild name the first Contract as the next action
-> inspect an unlocked Contract and choose difficulty without changing state
-> confirm one bounded Contract with 52 Coin and Line capacity four
-> enter one stable Market with three Recruit, four equipment and three battle offers
-> inspect an offer without buying from the list
-> review exact Recruit identity, Profession, Trait benefit/cost, attributes,
starting item, price and Company/Line effect
-> Cancel to the same offer or confirm one atomic hire
-> complete a second independent review and hire
-> stop in the same Market at Company four, Line capacity four and 24 Coin
```
Only one row may be `IN_PROGRESS`. A failed check keeps that row active.
<!-- markdownlint-disable MD013 -->
| Substep | Status | Owned product boundary | Narrow acceptance check | Commit boundary |
| --- | --- | --- | --- | --- |
| `DEV-3A` Contract foundation | `IN_PROGRESS` | One authoritative migration of the verified Company store adds zero-or-one active Contract, deterministic first-Market state, 52 Coin, Line capacity four, operation receipts and retry-safe persistence without changing the two existing Recruit records | `ABG_DEV3_CONTRACT_OK`; v1 migration, create/retry/conflict, candidate/backup recovery, exact 3/4/3 board and restart stability pass | Focused Contract/Market domain service, persistence test, plan/checkpoint update and push |
| `DEV-3B` Guild and Contract choice | `PENDING` | The real Guild identifies the next action, opens one unlocked Contract review, changes difficulty without commitment and creates the bounded Contract only after explicit confirmation | `ABG_DEV3_GUILD_OK`; Continue/Guild/review/cancel/confirm/restart and visible disabled-reason paths pass with no Market purchase or DEV-4 state | Focused Guild/Contract UI, input test, plan/checkpoint update and push |
| `DEV-3C` Stable Market and Recruit review | `PENDING` | A physical requisition surface exposes all 3 Recruit, 4 equipment and 3 battle offers; list actions only inspect, while Recruit review shows exact decision data and Cancel returns to the invoking stable offer | `ABG_DEV3_MARKET_OK`; board identity, list/review separation, exact price/affordability/capacity copy, cancel/focus restoration, localization and restart pass | Focused Market/review UI, behavior test, plan/checkpoint update and push |
| `DEV-3D` Atomic first hires | `PENDING` | Two separately reviewed affordable level-1 Recruit offers each create one idempotent receipt and update Coin, ownership and offer state atomically from `Company 2` to `3` to `4` while Line capacity remains four | `ABG_DEV3_HIRE_OK`; exact combined 28 Coin cost and 24 Coin remainder, double-confirm, new-ID retry, stale/unaffordable/capacity-display and interrupted-write recovery pass | Focused hire transaction/UI feedback, persistence/input test, plan/checkpoint update and push |
| `DEV-3E` Guild/Market candidate | `PENDING` | The source-bound Title/Continue -> Guild -> Contract/difficulty -> Market -> two separate Recruit reviews/hires path is responsive, persistent and stops before formation/risk | Applicable DEV-1/2/3 markers, parsed touch, strict diagnostics and a bounded normal-render state set pass from clean committed source | Candidate evidence closure commit and push |
<!-- markdownlint-enable MD013 -->
DEV-3 owns the minimum Company-store migration, Contract/Market domain service,
Guild/Contract/Market/Recruit-review runtime in `runtime/entry/`, focused tests
under `runtime/tests/dev3/`, and existing checkpoint/contract/ledger sections.
It reuses the accepted painted Guild scene, unified compact Recruit family and
precise inset/frame/button grammar. Equipment and battle offers are inspectable
but cannot be purchased or committed in DEV-3. Automatic formation, Party-line
editing, risk selection, battle, result, knockout recovery, second-cycle
management, later Regions, bulk assets, devices, packages and release remain
outside DEV-3.
DEV-3 verification increases in cost from static/domain persistence, to the
active focused behavior/input test, then the source-bound DEV-3 path and a
small representative normal-render matrix. The preserved full FG-4 suite is
not repeated during ordinary DEV-3 substeps; it runs once at the final
applicable regression boundary. Any check expected to exceed 60 seconds is
named with scope, purpose and expected duration before it starts.
DEV-3 final handoff is exactly `ABG DEV-3 candidate ready`. It requires focused
pushed commits, `HEAD == upstream`, a clean worktree, no owned test processes
and aligned plan/checkpoint/ledger facts. Human visual/comprehension/fun,
device, package, store and release gates remain `OPEN`.
### DEV-3 Issue Register
| ID | Status | Boundary |
| --- | --- | --- |
| `DEV3-I01` | `ACTIVE_DEV-3A` | The DEV-2 Company file intentionally has no active Contract. DEV-3A must migrate it in one authority rather than create unsynchronized Company and run files. |
| `DEV3-I02` | `FROZEN_LEGACY` | Historical FG-4 Contract services retain superseded roster-loss semantics and cannot be adopted as current authority without conversion in their named later step. |
| `DEV3-I03` | `ACTIVE_RECURRENCE_CHECK` | Guild and Market must preserve character-first staging, stable content/frame insets and differentiated commands. A card/text wall, recommended Recruit, combined `Hire two`, list-row purchase or silent disabled control is prohibited. |
| `DEV3-I04` | `OPEN_HUMAN_GATE` | Automated/runtime evidence cannot grant understanding of Company versus Line capacity, purchase choice quality, visual acceptance or willingness to continue. |
<!-- Historical section source: DEVELOPMENT_LEDGER; retained in Git history. -->
## Aetherbound Guild Development Ledger
@@ -1211,3 +1273,18 @@ they are not duplicated here.
`ABG DEV-2 candidate ready`. DEV-3 requires a separately activated durable
plan and cannot reuse this closure as authorization to skip its own focused
commit boundaries.
### 2026-08-17 - DEV-3 Guild And First Market Activated
- The Owner authorized autonomous sequential development through DEV-6 and
requested one durable Goal plus a complete morning handoff. DEV-3 is the only
active milestone; later milestones advance only after focused verification,
commit and push of the earlier boundary.
- DEV-3 stops after two separate first-Market Recruit transactions: the
persistent Company advances from two to four owned Recruits, Line capacity
remains four, and exact Coin advances from 52 through the two protected
prices totaling 28 to 24. No offer is recommended and no combined purchase
exists.
- `DEV-3A` first adds one migrated authoritative Contract/Market state around
the verified Company file. DEV-4 formation/risk, DEV-5 battle/result and
DEV-6 second-cycle management remain frozen.