Repository navigation
Releases
semantic-schema 0.6.0
Manifest schema admits where and record_validation (PLAT-1482, FR-149-AC-10/11, #355).
semantic-core 0.4.4
semantic-core 0.4.4 / semantic-schema 0.4.3
Point release: first release published tokenless over npm Trusted Publishing (OIDC). The publish job no longer has any token path. No schema changes since 0.4.0.
semantic-core 0.4.3
semantic-core 0.4.3 / semantic-schema 0.4.2
Point release: package READMEs with generated figures for both packages, and a corrected package description. No schema changes since 0.4.0 (see the 0.4.0 notes for the {kind, value} form).
semantic-core 0.4.2
semantic-core 0.4.2 (point revision; 0.4.0 changes apply)
The wire form moves to tagged {kind, value} objects, matching quire-rs FR-081 and the quire-fixtures goldens. Published 0.3.3 carries the old form and cannot be reused.
Breaking changes:
TypeRef.targetis nowTypeRefTarget: a taggedoneOfof{kind: "SemanticId", value: <SemanticId>}or{kind: "KernelScalar", value: <KernelScalar>}(newTypeRefTarget.json). It was an untaggedanyOfof the two bare strings.MinConstraint,MaxConstraint,ExclusiveMinConstraintandExclusiveMaxConstraintvalues are now{kind: "number", value: <number>}or{kind: "string", value: <string>}(newMin/Max/ExclusiveMin/ExclusiveMax ConstraintValue.json). They were a bare number or string.EnumValuesConstraint.valuesentries are nowEnumValuesConstraintValues:{kind: "string" | "number" | "boolean", value}(newEnumValuesConstraintValues.json). They were a bare string, number or boolean.- Each
ConstraintDeclentry is now wrapped as{kind: "<XConstraint>", value: <record>}(for example{kind: "MinConstraint", value: {...}}) in a taggedoneOf. It was an untaggedanyOfof the constraint records, described as discriminated onkeyword. - Six new schema documents (31 -> 37):
TypeRefTarget,MinConstraintValue,MaxConstraintValue,ExclusiveMinConstraintValue,ExclusiveMaxConstraintValue,EnumValuesConstraintValues. kernel-scalars.jsonwording (STD-399): Duration bounds and serialization now say exact elapsed time (days, hours, minutes, seconds, at most nine fractional-second digits) serialized as an ISO 8601 duration string; Bytes bounds areminLength and maxLength in octetsand serialization is canonical padded base64 (RFC 4648 section 4, FR-032); JSON bounds read "any JSON value of any kind".- Every schema
$id/$refis now underhttps://schemas.agent-ix.org/semantic-core/0.4.2/.
Consumers (quoin, spec-objects-*, quire-rs fixtures) must move to semantic-core/0.4.2 refs and the {kind, value} forms above; bare-string 0.3.x documents no longer validate.
semantic-core 0.4.1
semantic-core 0.4.1 (BREAKING vs 0.3.x)
The wire form moves to tagged {kind, value} objects, matching quire-rs FR-081 and the quire-fixtures goldens. Published 0.3.3 carries the old form and cannot be reused.
Breaking changes:
TypeRef.targetis nowTypeRefTarget: a taggedoneOfof{kind: "SemanticId", value: <SemanticId>}or{kind: "KernelScalar", value: <KernelScalar>}(newTypeRefTarget.json). It was an untaggedanyOfof the two bare strings.MinConstraint,MaxConstraint,ExclusiveMinConstraintandExclusiveMaxConstraintvalues are now{kind: "number", value: <number>}or{kind: "string", value: <string>}(newMin/Max/ExclusiveMin/ExclusiveMax ConstraintValue.json). They were a bare number or string.EnumValuesConstraint.valuesentries are nowEnumValuesConstraintValues:{kind: "string" | "number" | "boolean", value}(newEnumValuesConstraintValues.json). They were a bare string, number or boolean.- Each
ConstraintDeclentry is now wrapped as{kind: "<XConstraint>", value: <record>}(for example{kind: "MinConstraint", value: {...}}) in a taggedoneOf. It was an untaggedanyOfof the constraint records, described as discriminated onkeyword. - Six new schema documents (31 -> 37):
TypeRefTarget,MinConstraintValue,MaxConstraintValue,ExclusiveMinConstraintValue,ExclusiveMaxConstraintValue,EnumValuesConstraintValues. kernel-scalars.jsonwording (STD-399): Duration bounds and serialization now say exact elapsed time (days, hours, minutes, seconds, at most nine fractional-second digits) serialized as an ISO 8601 duration string; Bytes bounds areminLength and maxLength in octetsand serialization is canonical padded base64 (RFC 4648 section 4, FR-032); JSON bounds read "any JSON value of any kind".- Every schema
$id/$refis now underhttps://schemas.agent-ix.org/semantic-core/0.4.1/.
Consumers (quoin, spec-objects-*, quire-rs fixtures) must move to semantic-core/0.4.1 refs and the {kind, value} forms above; bare-string 0.3.x documents no longer validate.
semantic-core 0.4.0
semantic-core 0.4.0 (BREAKING vs 0.3.x)
The wire form moves to tagged {kind, value} objects, matching quire-rs FR-081 and the quire-fixtures goldens. Published 0.3.3 carries the old form and cannot be reused.
Breaking changes:
TypeRef.targetis nowTypeRefTarget: a taggedoneOfof{kind: "SemanticId", value: <SemanticId>}or{kind: "KernelScalar", value: <KernelScalar>}(newTypeRefTarget.json). It was an untaggedanyOfof the two bare strings.MinConstraint,MaxConstraint,ExclusiveMinConstraintandExclusiveMaxConstraintvalues are now{kind: "number", value: <number>}or{kind: "string", value: <string>}(newMin/Max/ExclusiveMin/ExclusiveMax ConstraintValue.json). They were a bare number or string.EnumValuesConstraint.valuesentries are nowEnumValuesConstraintValues:{kind: "string" | "number" | "boolean", value}(newEnumValuesConstraintValues.json). They were a bare string, number or boolean.- Each
ConstraintDeclentry is now wrapped as{kind: "<XConstraint>", value: <record>}(for example{kind: "MinConstraint", value: {...}}) in a taggedoneOf. It was an untaggedanyOfof the constraint records, described as discriminated onkeyword. - Six new schema documents (31 -> 37):
TypeRefTarget,MinConstraintValue,MaxConstraintValue,ExclusiveMinConstraintValue,ExclusiveMaxConstraintValue,EnumValuesConstraintValues. kernel-scalars.jsonwording (STD-399): Duration bounds and serialization now say exact elapsed time (days, hours, minutes, seconds, at most nine fractional-second digits) serialized as an ISO 8601 duration string; Bytes bounds areminLength and maxLength in octetsand serialization is canonical padded base64 (RFC 4648 section 4, FR-032); JSON bounds read "any JSON value of any kind".- Every schema
$id/$refis now underhttps://schemas.agent-ix.org/semantic-core/0.4.0/.
Consumers (quoin, spec-objects-*, quire-rs fixtures) must move to semantic-core/0.4.0 refs and the {kind, value} forms above; bare-string 0.3.x documents no longer validate.
semantic-core 0.3.3
Added
Float32andFloat64kernel scalar targets in the TypeSpec grammar, scalar catalog, and generated JSON Schema.- Enum member names with single internal hyphens, preserving external spellings.
Changed
- Integer values and bounds use canonical integer strings; the declared bound range extends to signed 128-bit values.
- Decimal values use canonical decimal strings, with precision and scale capped at 38.
- Generated semantic-core schema IDs and references use the 0.3.3 version.
Release qualification
- The release workflow now installs its pinned SysML pilot and JRE inputs with SHA-256 verification and runs Node tests inside Poetry's Python environment.
- The 0.3.3 workflow passed its full test, lint, and package publish jobs on commit
6e2c98fca5d0d63a1226b75fc088cacee2259a87.
extraction-frontend 0.2.1
agent-ix-extraction-frontend (Rust) 0.2.1.
Consume it by tag: agent-ix-extraction-frontend = { git = "https://github.com/agent-ix/filament-core-data", tag = "extraction-frontend-v0.2.1" }.
Changes
- Moves to quire-rs 0.50.1 (semantic-schema 0.3.0, quire-code-parse 0.2.2); no behaviour change.
semantic-kernel 0.3.1
agent-ix-semantic-kernel (Rust) and @agent-ix/semantic-agent-ix__semantic-kernel (TypeScript) 0.3.1.
Changes
- The generated JSON Schema index no longer records a per-schema digest (a hash inventory of our own output).
- Generated against semantic-core 0.3.2.
semantic-kernel 0.3.0
agent-ix-semantic-kernel (Rust) and @agent-ix/semantic-agent-ix__semantic-kernel (TypeScript) 0.3.0.
Contents
- Breaking: the generated provenance block (backend version, fingerprint, digests, package identity) is no longer emitted in the TypeScript, Rust or Python kernel packages. The tool that generated an output is recorded at run time, not as a committed manifest.
- Generated against semantic-core 0.3.2;
toolchain.jsonis no longer part of the bundle.