levelset/src/schema/ at main · russ.fugl.dev/levelset · Tangled

russ.fugl.dev / levelset

0

A functional toolkit for authoring resource-leveling algorithms — compose constraint and scoring blocks, enumerate feasible schedules

0

levelset / src / schema /

at main 11 files

Russ T. Fugal fix(provenance): preserve unknown levelset keys across the JSON round trip 6d ago

fix(provenance): preserve unknown levelset keys across the JSON round trip RunProvenanceSchema (and its warning items) parsed with key-stripping z.object, so a levelset block written by a newer levelset version — or annotated by app tooling — was silently truncated to this version's fields on read → write. Parse with z.looseObject so unknown keys survive the round trip; garbage that fails the known-field contract is still dropped whole, as documented.

6 days ago

feat(schema): entity schemas as the single source of truth Task, Resource, Assignment, Calendar, Relation, and ProjectFile schemas. These are the single source of truth for the data model: the model-layer interfaces are derived from them via z.infer, so each shape has exactly one definition and the validators can never drift from the types. Optional fields are declared with `.optional()` and typed `T | undefined` so they round-trip cleanly under exactOptionalPropertyTypes.

4 months ago

feat(schema): zod enum, date, and duration schemas The leaf zod schemas the entity schemas build on. Enum schemas use z.enum, which under Zod v4 accepts native TypeScript enums directly, so the runtime validators share identity with the model enums. The date and duration schemas carry transforms, making parse/serialize part of validation rather than a separate step.

4 months ago

feat(schema): zod enum, date, and duration schemas The leaf zod schemas the entity schemas build on. Enum schemas use z.enum, which under Zod v4 accepts native TypeScript enums directly, so the runtime validators share identity with the model enums. The date and duration schemas carry transforms, making parse/serialize part of validation rather than a separate step.

4 months ago

feat(leveling): embed run provenance in materialized projects Every LevelingRun.materialize output now carries a levelset metadata block: engine version, the filled run config (rerunnable — the reproducibility artifact), seed, achieved scorer values, analysis warnings, and search annotations. ProjectFileSchema gains the optional field and the JSON reader/writer round-trips it (non-parsing provenance is dropped on read rather than failing the file). Answers "why does this schedule look like this?" from the file itself, spaCy config.cfg-style.

6 days ago

feat(leveling): embed run provenance in materialized projects Every LevelingRun.materialize output now carries a levelset metadata block: engine version, the filled run config (rerunnable — the reproducibility artifact), seed, achieved scorer values, analysis warnings, and search annotations. ProjectFileSchema gains the optional field and the JSON reader/writer round-trips it (non-parsing provenance is dropped on read rather than failing the file). Answers "why does this schedule look like this?" from the file itself, spaCy config.cfg-style.

6 days ago

fix(provenance): preserve unknown levelset keys across the JSON round trip RunProvenanceSchema (and its warning items) parsed with key-stripping z.object, so a levelset block written by a newer levelset version — or annotated by app tooling — was silently truncated to this version's fields on read → write. Parse with z.looseObject so unknown keys survive the round trip; garbage that fails the known-field contract is still dropped whole, as documented.

6 days ago

feat(schema): entity schemas as the single source of truth Task, Resource, Assignment, Calendar, Relation, and ProjectFile schemas. These are the single source of truth for the data model: the model-layer interfaces are derived from them via z.infer, so each shape has exactly one definition and the validators can never drift from the types. Optional fields are declared with `.optional()` and typed `T | undefined` so they round-trip cleanly under exactOptionalPropertyTypes.

4 months ago

feat(schema): entity schemas as the single source of truth Task, Resource, Assignment, Calendar, Relation, and ProjectFile schemas. These are the single source of truth for the data model: the model-layer interfaces are derived from them via z.infer, so each shape has exactly one definition and the validators can never drift from the types. Optional fields are declared with `.optional()` and typed `T | undefined` so they round-trip cleanly under exactOptionalPropertyTypes.

4 months ago

feat(schema): entity schemas as the single source of truth Task, Resource, Assignment, Calendar, Relation, and ProjectFile schemas. These are the single source of truth for the data model: the model-layer interfaces are derived from them via z.infer, so each shape has exactly one definition and the validators can never drift from the types. Optional fields are declared with `.optional()` and typed `T | undefined` so they round-trip cleanly under exactOptionalPropertyTypes.

4 months ago

feat(schema): zod enum, date, and duration schemas The leaf zod schemas the entity schemas build on. Enum schemas use z.enum, which under Zod v4 accepts native TypeScript enums directly, so the runtime validators share identity with the model enums. The date and duration schemas carry transforms, making parse/serialize part of validation rather than a separate step.

4 months ago