RAPP Work organization seed · public synthetic data

The Independent Game Studio

Run a seven-team independent studio around Mosslight Courier, an original offline route puzzle. Turn synthetic first-session feedback into a bounded onboarding revision with playable source, readable art, opt-in sound, and reproducible regression evidence.

7 teams · 8 scoped workspaces · 10 tasks · 34 package files

Download organization seed Open verified AI join Global skill for your AI Complete seed JSON

This package is not an activated organization, a membership grant, or a running service. Native SDK plans and starter-file effects require owner approval. Joining never executes downloaded code.

Chant: islet-quiver-delta-jade-hearth-hearth-haven

Locator-only join QR for The Independent Game Studio — Give this QR to your AI to inspect the exact seed and its declared protocol.

Your first engagement

Mosslight Courier: make the first bridge legible

SYNTHETIC production case: eight authored first-session records suggest confusion about four-beat bridge timing and undo. The starter game already works. Improve onboarding and readability without adding accounts, a backend, new mechanics, or an invented playtest result.

All three original boards are solvable by the deterministic engine and are playable with arrows or WASD, Space, U, and R.
A release candidate opens directly from disk with no fetches, CDN, trackers, storage, server, or dependency install.
Bridge and carrying state are conveyed by text/symbol as well as color; generated audio is off by default.
The synthetic baseline remains five completions out of eight, with five bridge stalls; no real improvement is claimed without new observation.
A producer records pass, rework, or hold against every supplied acceptance case before any separately approved publication.

An actual work scope for every team.

ProductionOwn the first-shift scope, review gates, and a conditional release decision without claiming a shipped product.
Game DesignSpecify understandable bridge, carrying, delivery, and undo rules within the existing three-board game.
Game EngineeringMaintain the deterministic engine and keyboard-first offline browser build.
Art and ReadabilityCreate original high-contrast symbols and a small coherent visual asset system.
AudioSpecify restrained, opt-in, locally synthesized event cues with a silent fallback.
Quality AssuranceCheck solvability, input handling, no-network behavior, accessibility limits, and regressions.
Player ResearchSeparate the synthetic feedback exercise from real observations and design the next consent-based playtest.

The Organization routes through native workspace pointers. Team ownership stays in team workspaces; shared case data stays in the separate casework workspace.

Starter work and acceptance.

Freeze a two-day first-shift revision · production · Ready to claim

Turn the production brief into an in/out scope and review sequence. Preserve the playable reference and treat the synthetic records as a rehearsal, not validation.

Inputs: starter/case/production.json, starter/ops/release-checklist.md

Outputs: deliverables/first-shift-scope.md

Depends on: No prerequisites

Names the two-day cap, all seven team owners, and the no-network/no-new-mechanics constraints.
Lists publication and real participant recruitment as separate owner-approved effects.

Reproduce the authored feedback baseline · player-research · Waiting on prerequisites

Run the local feedback utility and inspect every record. Attach counts and a coding note distinguishing author-generated feedback from observed research.

Inputs: starter/data/playtests.csv, starter/tools/feedback_report.py, deliverables/first-shift-scope.md

Outputs: deliverables/feedback-baseline.json, deliverables/feedback-coding.md

Depends on: lock-first-shift

Reports eight records, five completions, five bridge stalls, and three undo discoveries.
Explains that the sample cannot establish market demand or an actual usability improvement.

Specify bridge and carrying onboarding · design · Waiting on prerequisites

Write an exact first-minute interaction specification using the current four-beat bridge rule. Include blocked movement, standing on a closing bridge, depot reload, and undo.

Inputs: starter/design/rules.md, starter/case/production.json, deliverables/feedback-baseline.json, deliverables/feedback-coding.md

Outputs: deliverables/onboarding-spec.md

Depends on: read-synthetic-feedback

A player can determine whether the next bridge entry is legal from visible text.
Each rule has an example action/state pair and does not change the three level layouts.

Produce a symbol-complete mini atlas · art · Waiting on prerequisites

Revise the original courier SVG and palette into a compact, self-authored atlas or symbol sheet for the specified states. Avoid external fonts and borrowed game IP.

Inputs: starter/art/courier.svg, starter/art/palette.json, deliverables/onboarding-spec.md

Outputs: deliverables/courier-atlas.svg, deliverables/readability-notes.md

Depends on: revise-bridge-onboarding

Contains distinct depot, courier, undelivered beacon, delivered beacon, open bridge, and closed bridge symbols.
Every state remains distinguishable in monochrome and all SVG content is local.

Map optional synthesized cues · audio · Waiting on prerequisites

Review the existing Web Audio cue sheet against the onboarding specification. Specify short tones, volume bounds, and a no-audio fallback rather than importing audio.

Inputs: starter/audio/cue-sheet.csv, starter/game/game.js, deliverables/onboarding-spec.md

Outputs: deliverables/audio-map.json

Depends on: revise-bridge-onboarding

Includes blocked, loaded, delivered, and won events with durations no greater than 180 ms.
Requires a user opt-in and keeps every critical cue available in text.

Build the bounded onboarding revision · engineering · Waiting on prerequisites

Produce a revised engine/UI source pair from the working reference, incorporating the reviewed specification, symbol work, and optional cues. Preserve offline file opening and deterministic rules.

Inputs: starter/game/index.html, starter/game/game.js, starter/tests/game.test.js, deliverables/onboarding-spec.md, deliverables/courier-atlas.svg, deliverables/readability-notes.md, deliverables/audio-map.json

Outputs: deliverables/game.js, deliverables/index.html, deliverables/engineering-checks.json

Depends on: prepare-readable-art, specify-local-cues

The supplied engine tests still pass, including solver coverage for all three boards.
The revised HTML references only local files and supports keyboard restart, undo, wait, and level selection.
Records tests actually run separately from any unrun browser/device checks.

Execute rule and input acceptance cases · quality · Waiting on prerequisites

Use the regression table on the reference and revised build. Record state traces for bridge closure, illegal movement, delivery, winning, reset, and undo; do not mark manual browser checks passed without observation.

Inputs: starter/quality/acceptance.csv, starter/tests/game.test.js, deliverables/game.js, deliverables/index.html, deliverables/engineering-checks.json

Outputs: deliverables/regression-results.csv

Depends on: implement-onboarding

Every acceptance row has an actual result or explicit not-run status and reproduction steps.
No wall collision consumes a beat and each board can reach its win state.

Audit file-only release and accessibility · quality · Waiting on prerequisites

Inspect the candidate for network references, storage, external assets, focus behavior, optional sound, and non-color state cues. Use the checklist to separate automated evidence from browser and assistive-technology limits.

Inputs: starter/ops/release-checklist.md, deliverables/index.html, deliverables/game.js, deliverables/courier-atlas.svg, deliverables/regression-results.csv

Outputs: deliverables/offline-accessibility-review.md

Depends on: verify-game-regressions

Reports no network-capable gameplay code or remote assets.
Explicitly records whether keyboard-only, sound-disabled, narrow-screen, and screen-reader checks were performed.

Prepare the next real first-session test · player-research · Waiting on prerequisites

Write a small prospective test plan, not fabricated results. Ask participants to load, cross a bridge, deliver, undo, and restart; define consent and the minimum evidence needed to compare against the synthetic exercise.

Inputs: deliverables/feedback-coding.md, deliverables/onboarding-spec.md, deliverables/regression-results.csv, starter/case/production.json

Outputs: deliverables/prospective-playtest.csv

Depends on: verify-game-regressions, revise-bridge-onboarding

Contains five observable tasks with neutral facilitator wording and completion/error fields.
Identifies all new observations as pending and requires approval before recruitment or data collection.

Record a conditional release decision · production · Waiting on prerequisites

Review the implementation, QA evidence, offline/accessibility review, and prospective test plan. Choose hold or a bounded candidate recommendation; do not publish or claim real player outcomes.

Inputs: deliverables/first-shift-scope.md, deliverables/regression-results.csv, deliverables/offline-accessibility-review.md, deliverables/prospective-playtest.csv, starter/ops/release-checklist.md

Outputs: deliverables/release-decision.md

Depends on: audit-offline-release, plan-observed-playtest

Lists unresolved risks and every failed or unrun case.
Any publication recommendation remains conditional on explicit owner approval and does not mislabel the seed as a shipped commercial game.

Included starter artifacts.

These are files in the ZIP, not promises to generate them later. Reference examples do not mean the engagement is complete.

README.md 2,509 bytes
art/courier.svg 942 bytes
art/palette.json 557 bytes
audio/cue-sheet.csv 315 bytes
case/production.json 954 bytes
data/playtests.csv 842 bytes
design/rules.md 2,116 bytes
game/game.js 7,947 bytes
game/index.html 5,576 bytes
ops/release-checklist.md 1,520 bytes
quality/acceptance.csv 1,905 bytes
tests/game.test.js 8,569 bytes
tools/feedback_report.py 2,588 bytes

Package SHA-256: 12f9c2805e88c0e7b1e0e512640347694e33d4f2d80e7ccd548533434ceb9df8

Initialize with the RAPP Work SDK.

Inspect seed.json, initialize.json, and the exact dependency pins.
Choose your owner label and a new destination. Use the installed, verified SDK to plan the Organization and member Workspaces.
Approve complete native plans and their exact digests before applying. Review declared template copies and pointer registrations separately.
Claim a ready task with a capable authorized AI host, produce the requested output, and attach actual acceptance evidence.

No private membership, signing, spending, external communication, publication, or federation activation is granted by this seed.

Or boot it in a RAPP Brainstem.

This seed also ships as a boot Egg: a RAPP/1 organism Egg holding the exact seed record, a soul written from it, and the generic SeedRunner organ. A standard RAPP Brainstem hatches it and runs the same seed flow for you, with the same pinned SDK and the same owner approvals.

Install the standard Brainstem: curl -fsSL https://kody-w.github.io/rapp-installer/install.sh | bash
Download the boot Egg (SHA-256 1ddd053520788ca6a0e1253bc06b49b81c2cf7a9cd88b6cab974bb27df4ae588) and the hatcher (SHA-256 49b210e0c762eefad2602c3c1db93ab00d73d7edd5cd353c703fb408352a07d0). Check both hashes before running anything.
Plan the hatch: python3 hatch_seed.py --egg independent-game-studio.boot.egg. It verifies the Egg with the pinned RAPP/1 reference and prints every effect, how to reverse it, and a plan digest. Nothing changes yet.
Hatch with that exact digest: python3 hatch_seed.py --egg independent-game-studio.boot.egg --apply <plan_digest>. Your Brainstem gets its own instance identity, grown from Egg 707c00ca97d73a33…, and the SeedRunner organ.
Ask your Brainstem to run the seed. SeedRunner verifies it, plans the Organization and its Workspaces, and shows you an activation digest; nothing is created until you approve that exact digest.

The boot Egg grants no authority and runs nothing by itself. Boot record JSON.