Skip to content

modules: tech tiers - #8490

Draft
keithharvey wants to merge 1 commit into
hello_pawnsfrom
tech
Draft

modules: tech tiers#8490
keithharvey wants to merge 1 commit into
hello_pawnsfrom
tech

Conversation

@keithharvey

Copy link
Copy Markdown
Collaborator

Tech Core is a build feature, not a sharing rule: it gates construction by tier and shows the tier in its own panel.

The tier/rate line is where the old file split — resolving a tier-varying modoption is tech's; the tax rate that consults it is what a transfer costs and travels with transfer.

@github-actions

github-actions Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

Integration Test Results

17 tests  +2   8 ✅ +1   16s ⏱️ +12s
 1 suites ±0   8 💤 ±0 
 1 files   ±0   1 ❌ +1 

For more details on these failures, see this check.

Results for commit f2b7b25. ± Comparison against base commit a70c9ac.

♻️ This comment has been updated with latest results.

Tech Core is a build feature, not a sharing rule: it gates construction
by a team's tier and shows the tier in its own panel. It leaves sharing
with one edge behind it — transfer reads a team's tier to price a
transfer — and nothing reads back.

The tier/rate line is where the old file split. Resolving a tier-varying
modoption is tech's; the tax rate that consults it is what a transfer
costs, and travels with transfer.

Unit content stays at its engine paths. Module code loads through the
manifest shims, but unitdefs do not — the engine reads units/ and
unitbasedefs/ directly, so moving them under the module would leave the
content unloadable to make a directory tidier.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant