Mind packages
How source, guidance, rules, signatures, and provenance fit together.
A Mind package is a versioned policy artifact. It is not a model checkpoint and it is not a raw archive of everything a person has written.
Canonical reading path: Read What is LMP? first for the full narrative. This page is the focused package reference.
The complete schema, review order, release metadata, package layers, and distribution contract are maintained canonically in Mind Vault. This page keeps only the conceptual distinction; use Mind Vault when you are authoring or validating a package.
Think of it as the compiled form of an engineering point of view. It can say what a team values, where that preference came from, what the agent should do, and which parts can be checked by a machine. The package should be small enough to load during a run and rich enough to explain its own decisions.
The conceptual model
The package is the compiled form of an engineering point of view:
- Identity names the profile, version, and publisher.
- Guidance gives an agent explicit, bounded instructions.
- Rules define deterministic checks and severities.
- Provenance records the source and the interpretation.
- Integrity lets the consumer detect tampering before activation.
The active path loads the compact compiled policy. Larger source histories can remain content-addressed in registry or cache storage and be retrieved during review; they are not copied wholesale into every agent context.
Keep three statements separate when reviewing a package:
- A public source makes an observable recommendation.
- The package author interprets that recommendation as a preference.
- A rule makes a bounded part of that interpretation testable.
The source does not become an endorsement of LMP merely because it appears in a package. Preserve attribution and license requirements, and document the trade-off behind each rule.
Compile before activation
The Mind compiler normalizes source records, validates the schema, computes a content digest, and emits a deterministic bundle. Compilation should fail on an incomplete or ambiguous package rather than silently inventing semantics. The signed package, fixtures, and review metadata are the evidence that a profile is ready to activate. The complete field contract and review sequence are maintained in Mind Vault.
