RPG OS v0.8.0

RPG OS v0.8.0 — integrated agent state, experimental playtest release

This build integrates independent agent state throughout the campaign lifecycle and is ready for human campaign playtesting. It remains experimental: reliable NPC portrayal, enjoyable pacing and continuity across models must be assessed through actual play. No scripted behavioral trial schedule is a prerequisite for using it.

Download RPG_OS_v0.8.0.zip from this release and extract it into its own folder. Start with Quick start, read How RPG OS works, or use the upgrade guide for an existing campaign.

What changes in play

The GM establishes materially needed, genuinely unfixed agent facts through the accepted source or procedure before using them to resolve a response. It retains individual circumstances, aims, beliefs and relationships in their existing authorities and changes them for actual causes.

A courteous coworker can remain personally distant while developing professional trust. Relevant evidence can change a belief. An established goal and an actual opportunity can lead to initiative. Neither the player's desired outcome nor repeated equivalent attempts automatically create progress, resistance or a new random chance.

There is no compulsory trait vector, extra startup read, world-wide NPC tick, retrospective cast rewrite or automatic checkpoint.

Integrated lifecycle

• A compact consolidated core rule and cold OS/AGENT_STATE.md explain establishment, portrayal, causality, randomness and retention.
• Quick start, Guided and Detailed share one adaptive proposal and protected bind. Opening state uses the existing MODULE baseline; current people and systems retain their existing INSTANCE owners.
• Worldbuilding distinguishes capabilities, culture, individual facts, deliberately unfixed properties and missing sources. Source visuals govern their documented appearance scope, not invented personality.
• Random methods require defined applicable outcomes and actual input. Freeform judgment remains available and honestly labeled.
• Saving preserves established mixed relationships, qualified beliefs, relevant changes and sources. Fresh resumption and scene handover use those results instead of generating the person again.
• An interrupted setup retains its exact pending generation/result route through recovery. Restoring pre-bind files alone does not discard selected determinations or permit a silent reroll; completion or explicit setup cancellation/replacement resolves the pending bind.
• A v0.8 upgrade procedure preserves the old campaign and its runtime, applies reviewed generic changes in a separate copy and retains accepted state and history.
• An optional real-campaign playtest guide supports ordinary play and switching models at completed saves or through handover, with lightweight incident notes.
• The mechanics guide adds an agent-state lifecycle diagram; public setup, installation, commands and contribution guidance describe the implemented workflow.
• Structural, handover and packaging checks cover the new generic file inventory and relevant retained-record paths. Actual results are reported in Verification.
• Packaging preserves committed file bytes under Windows checkout preferences without changing Git settings. The public issue form accepts brief campaign incidents and fixes its version-placeholder indentation.

Retention and scope

Ordinary PLAY still writes no campaign files. New state remains in conversation until an authorized save completes. A requested CHECKPOINT preserves the complete accepted present and keeps the previous archive evidence boundary; it does not preserve missing transcript wording.

This release does not implement the proposed automatic protected-establishment checkpoint experiment, an additional live state layer, or an encrypted/private model memory. Source files remain frozen during scene handover; receiver-side developments must be captured in the permitted return. A genuinely lost determination is a retention gap, not permission to claim the original result was recovered.

The protocol preserves provider-neutral presentation wording and the campaign's accepted authorship and operator terms.

Compatibility and evidence

The v0.7.1–v0.7.3 current-save and agreement formats remain compatible. Existing people, module baselines and accepted relationships are not rerolled or retrospectively completed. See the upgrade guide; older formats retain their existing migration route.

Engineering checks remain part of delivery. Human campaign testing is the primary next evaluation of narrative quality and practical operation. Proposed behavioral cases and historical trials are not reported as new v0.8 results.

The distribution is an unbound fresh install containing Freeform and blank campaign/archive records. It includes no Tellus module, character, private campaign, transcript, personal policy or artwork. Documentation/protocol material retains CC BY 4.0 licensing; code/configuration retains MIT.