MTG RL / Engine workstream
Accepted complete cards, not merely enabled handlers
Loot, Eardrum Rattler and grouped-discard worker completions have been reported. Completion notices are not acceptance; do not repeat their implementation without checking the existing work.
Use Fateshaper Aspirant as a reference, then exercise Divining Duelist and Archive Arbiter through the same interface. Preserve engine-owned targeting, triggers and choices.
One owner implements and verifies its assigned module. Escalate missing shared capabilities rather than editing scattered core branches.
Batch cards behind the same missing capability. Existing blocker text is historical ledger data and may need reconciliation, not a fresh audit campaign.
Card acceptance alone is not evidence of complete rules or policy-adapter readiness. Full-game/PPO work remains deferred.
Every card not marked complete in the ledger. Filters above apply; no acceptance state can be changed here.
A family is a contribution boundary built around shared execution semantics—not color, creature type, or deck archetype. These three implemented cards all create an entry trigger whose selected mode determines its targets and effect.
These cards are already accepted: this is a hypothetical conversion example, not new card progress. Once the boundary is established, the same owner continues through suitable remaining families. New shared rules still require core work.
Read-only source: coordination/card-status.json. Rules text: data/cards/definitions.json. Counts are recomputed from individual card rows; no worker reports were accepted by this dashboard. Generated objects are not counted as additional catalog cards.
Families are proposed primary planning groups, derived from card text with a small representative-family override. Cards often span multiple mechanics. These groups do not establish independent module boundaries, full shared-mechanic support, or a final implementation order. Family progress counts cards, not rules completed. “Other” means grouping still needs attention.
“Complete” means accepted in the existing ledger, not reverified during dashboard creation. In-progress entries are unaccepted branch work at the ledger snapshot, not a claim that workers are still running. Blockers and evidence are shown verbatim and can be stale.
This is a standalone offline snapshot, not an automatically updating page. Regenerate from the project root with:python coordination/render_card_implementation.py
Then reopen or reload coordination/card-implementation.html. No engine code, acceptance ledger or project plan is changed by regeneration.