Draft preview No v1.0 artifact yet
A pack is a versioned artifact CleverMemory can read. The public format is intended to let you inspect where a pack came from, which terms apply to it, whether it has changed, and which product versions can read it. It also carries the public source information needed to check a proof-carrying answer: an answer that arrives with the machine-checkable derivation behind it.
The format stops there on purpose. How the engine interprets, searches, connects, or chooses information is the code and data that tie everything together, and that piece stays ours. Everything you need to check what it tells you is on this page.
What the public contract needs to cover#
- a stable identity for the pack and its records;
- enough type and direction information to preserve the meaning being exchanged;
- qualifiers that matter to the record, such as time, source, quantity, possibility, and negation;
- where a record appeared in its source document, since position in a table, heading, or exhibit can change what a record means;
- source references, attribution, and license notices;
- a versioned manifest and an artifact digest (the checksum that fingerprints the file); and
- an explicit failure when a reader cannot safely handle a version or required feature.
What remains private#
The pack contract does not publish the product's internal representation, language interpretation, search strategy, answer selection, reasoning process, or pack-building methods. That stays inside the product boundary.
The contract also cannot grant rights to third-party data. Each released pack will carry its own source record and terms. The Packs page is the current planning inventory.
Release checks#
Before a v1.0 format is published, the public artifacts will need to show that:
| Check | What must hold |
|---|---|
| Identity | Records keep their declared identity within the pack's stated scope. |
| Meaning | Direction, type, and required qualifiers survive a write-and-read cycle. |
| Position | A record's declared location in its source document survives a write-and-read cycle. |
| Provenance | A public record can be traced to the source reference declared by its pack. |
| Source terms | Attribution and source-specific restrictions stay visible. |
| Integrity | A consumer can verify the artifact against its manifest and digest. |
| Compatibility | Unsupported versions or required features fail clearly instead of being misread. |
| Repeatability | The same pinned artifact and reader produce the same public observations. |
These checks say nothing about answer quality, production reliability, scale, or regulatory suitability. Those require separate evaluation.
Planned release set#
A complete first release is expected to include:
- the format specification;
- the manifest and provenance rules;
- small compatibility fixtures with expected results;
- a public reader or validator; and
- source-specific documentation for any packs that are actually released.
Names, encoding, packaging, version ranges, and release licenses are still subject to change. Before v1.0, there is no compatibility promise.
Current status#
The contract is still moving with the product. There is no normative v1.0 document, reference tool, or public conformance evidence today. The format will freeze when its tests and release artifacts are ready, not on a calendar date.
See Updates for dated changes or Evaluation for the rules public results will follow.