Skip to content

Clearhaven Mine #25

Description

@mamoru

Architecture amendment — one authored content source (2026-08-13)

Initiative atrinik/atrinik#357 supersedes every future live-branch instruction below. atrinik/content@main is the sole mutable authored source for replacement and Classic targets. Future authored changes land only on main; supported Classic artifacts are deterministically derived from the same immutable main revision. Do not create, restore, author, backport, validate, or publish through a live 1.x branch.

Exact historical 1.x commits, tags, releases, assets, preserved local snapshots, provenance, parity records, and comparisons remain valid immutable evidence. This amendment changes no other feature, balance, lore, compatibility, licensing, validation, or ownership acceptance criterion.

Important

The gameplay/authored-content decisions in this issue are preserved. This revision changes only the technical implementation path for the fresh MIT Go/Rust replacement program. atrinik/content remains separately/mixed licensed data; MIT engine/tooling code does not relicense the corpus.

Replacement implementation contract

Preserve the Clearhaven Mine and create-bomb gameplay/content specification. Build it from generic Go activity, item/inventory, spell/effect/explosion, trigger/action, quest/dialogue, and encounter contracts; add a focused native Go primitive issue only if a durable gap remains. No bespoke runtime Python by default.

Common migration gates

  • Stable authored identities and behavior remain the source of truth; localized/rendered text and filesystem order are never identity.
  • Content is parsed, validated, transacted, and compiled by released content-toolkit; production Go/Rust consumers do not add private source parsers.
  • Runtime authority belongs to native Go services and bounded compiled definitions/CEL; Starlark is considered only through the residual go/no-go issue.
  • Verification uses deterministic compiler/conformance fixtures and wrapper-managed Go-server/Rust-client scenarios.
  • Verified original past work by an approved MIT provenance grantor may be copied, migrated, translated, or relicensed under MIT only through the merged complete-history provenance directive; all asset/data notices remain exact.

Content release-line scope

This future feature targets content@main and the canonical replacement stack. It is not automatically backported to content@1.x; any separately approved classic maintenance uses a linked pull request under #45, preserves the same gameplay/content decision and attribution, and validates only compatible classic consumers.

Preserved product/design specification and historical implementation notes

Add mineshaft down the well, preferably with create bomb spell as reward from
an old miner.

Atrinik Bugzilla 114

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

Fields

Priority

None yet

Effort

None yet

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions