Validate the lay Office output against its fixture #178

New issue

Open

opened 2026-07-01 00:56:48 +00:00 by manlycucumber · 0 comments

manlycucumber commented

2026-07-01 00:56:48 +00:00

(Migrated from github.com)

Problem

As an original arrangement there is no external oracle, so a self-consistent reference fixture must be established and guarded against regression.

Acceptance criteria

A reference fixture for the lay Office is established with provenance
Assembled output is compared to the fixture in CI
Source attribution is verified per part
Divergences fail the build

Notes

Fixture is the contract for an own-composed product.

## Problem As an original arrangement there is no external oracle, so a self-consistent reference fixture must be established and guarded against regression. ## Acceptance criteria - [ ] A reference fixture for the lay Office is established with provenance - [ ] Assembled output is compared to the fixture in CI - [ ] Source attribution is verified per part - [ ] Divergences fail the build ## Notes Fixture is the contract for an own-composed product.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

Directorium/Core#178

No description provided.

Rows
Columns