You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Replace supported offline Python content workflows in bounded domain groups with the MIT toolkit while preserving useful behavior and improving one-owner safety.
Scope and invariants
Inventory current content/tools entry points and classify parser/model, schema, catalog, validation, collection, runtime build, world audit, syntax evaluation, interfaces, tests, and obsolete workflows.
For verified approved-grantor modules, choose direct MIT reuse, staged reuse as a parity oracle, or Rust translation; retain provenance links and attribution.
Keep server runtime Python migration separate; this issue is offline authoring/build tooling.
Acceptance criteria
Every supported old entry point maps to a released toolkit command/API or an explicit retirement decision.
Behavior/output differences are reviewed semantic improvements, not accidental omissions; fixtures are licensed/provenanced.
Content CI and packaging run without old Python tooling for migrated groups.
No permanent dual parser/catalog/transaction path remains after a group closes.
Whole-corpus runtime and performance meet recorded budgets.
Dependencies and parallelization
Depends on grant audit #2 and core APIs. Parallelize by workflow group after shared parser/catalog/transaction contracts freeze.
Licensing
Toolkit code is MIT. Original past contributions by a person listed in the merged approved MIT provenance-grantor registry in atrinik/atrinik#275 may be copied, migrated, translated, or relicensed under MIT only after a complete, non-shallow Git-history audit, including renames and moves, proves the selected material is that grantor's solely authored original work and contains no embedded third-party or conflicting-licensed material. Record the exact evidence, applicable grantor, and destination. Mixed authored data and fixtures retain their actual licenses.
Outcome
Replace supported offline Python content workflows in bounded domain groups with the MIT toolkit while preserving useful behavior and improving one-owner safety.
Scope and invariants
content/toolsentry points and classify parser/model, schema, catalog, validation, collection, runtime build, world audit, syntax evaluation, interfaces, tests, and obsolete workflows.Acceptance criteria
Dependencies and parallelization
Depends on grant audit #2 and core APIs. Parallelize by workflow group after shared parser/catalog/transaction contracts freeze.
Licensing
Toolkit code is MIT. Original past contributions by a person listed in the merged approved MIT provenance-grantor registry in atrinik/atrinik#275 may be copied, migrated, translated, or relicensed under MIT only after a complete, non-shallow Git-history audit, including renames and moves, proves the selected material is that grantor's solely authored original work and contains no embedded third-party or conflicting-licensed material. Record the exact evidence, applicable grantor, and destination. Mixed authored data and fixtures retain their actual licenses.