Quiet File Team Setup Kit Generator

Generate a configured Quiet File Team starter ZIP (several AI bots sharing one computer through files) with ready rules, guided installation, examples and acceptance checks. $29 per successfully generated kit; no scraping and no model calls.

How to use this

1. Fill Roster (TEAM_IDS, default lead builder helper), IANA time zone (TEAM_TZ, default UTC) and keep Coordinator as lead (it must be on the roster). displayName is an optional generic label.
2. Allow a maximum run charge of at least $29 (one setup_kit event per successful kit; nothing is charged for failed validation or generation) and click Start.
3. Download OUTPUT.zip from the run's key-value store, extract it to a NEW local folder, review team.conf, then follow guidance/references/install-guide.md and the acceptance checklist. The kit does not install schedules or run agents.

For AI agents

Field	Value
Purpose	Generate a configured file-first team kit ZIP (core scripts + guidance) from a roster, time zone and coordinator.
Use when	A user wants a ready-to-unpack Quiet File Team folder instead of configuring the free core by hand.
Do not use when	The free core is enough (git clone https://github.com/pandadad0214/quiet-file-team), or you need scheduling, hosting or messaging.
Inputs	TEAM_IDS, TEAM_TZ, coordinator (lead), optional displayName
Outputs	OUTPUT.zip in the key-value store; dataset row with archive key, roster, zone, coordinator, edition note and checksum
Cost	$29 per successfully generated and persisted kit (setup_kit).

Switch editions

Free path: git clone https://github.com/pandadad0214/quiet-file-team.git, set TEAM_DIR to the new checkout and follow its README. No purchase is needed for the core.

Free → paid generator: on this page enter roster and zone, keep lead, allow at least $29, run and download OUTPUT.zip. It includes the free core plus optional paid guidance. Deploy in a separate directory and practice before adopting. Environment overrides still win over generated config defaults. The fictional exercise uses the default roster even if your configuration differs.

Paid → free: back up existing data, install a clean free clone separately, review/re-enter active tasks deliberately and repoint routines. Remove optional guidance if unwanted; never overwrite operational logs with examples. Other editions: a free MCP companion (github.com/pandadad0214/quiet-file-team-mcp) and a $29 one-time Agensi setup skill (agensi.io/skills/quiet-file-team-setup-kit) that guides your agent through the same setup in your own folder.

Boundaries

One trusted shared Linux machine, Bash 4+, GNU tools and reliable local flock locks. Test suite uses ripgrep. Not remote transport, access control, encrypted storage, a scheduler or a hosted team. Roster labels do not authenticate identities. Only lead has coordinator authorization. Never put personal data or credentials in the bus. Input validation is a bounded syntactic guardrail, not a complete private-data detector.

For developers

src/generator.py is pure bounded generation; it never executes caller input. Assets are copied only from the generic free source and guidance draft, never an operational team. src/main.py persists and reads back the ZIP, persists dataset metadata, then calls Actor.charge(event_name='setup_kit', count=1) exactly once. A budget check occurs before persistence. No charge is made for input validation, generation or persistence failures. Distributed billing is not an atomic transaction: a billing rejection can leave a persisted kit, and a platform interruption after charging is governed by Apify; no refund promise is made.

Tests: python -m unittest discover -s tests -v. Local generation: python -m src.local OUTPUT.zip. Local generation makes no platform call or charge.