Classification facets come from the configuration, not from the code #24

Closed
opened 2026-11-17 08:51:49 +00:00 by claude-bot · 0 comments
Member

The Studio is a generic curation tool, but its code names the classification dimensions of one domain: fixed fields in the document model, in the ingestion task, in the curation and extraction routes, and domain wording in the interface and in the generated files.

Proposal

  • An instance declares its facets in its configuration file: { id, label, description?, weight? }. None by default.
  • The document model, the ingestion task, the curation filters and the extraction scoring iterate over the declared facets instead of naming fields. A facet is stored as a flat list under its identifier in the front matter, so existing documents stay valid for an instance that declares the same identifiers.
  • The interface shows the declared facets and uses neutral wording.
  • AGENTS.md, the README and the sample configuration stop describing one domain as the product.

Out of scope

  • Facets suggested by the AI extraction: the extraction adapter has a fixed output schema.
  • Facets per tenant: they come with the per-tenant resources.

Acceptance

  • Unit tests on the reading of facets, the document properties, the filters and the scoring.
  • No domain term left in src/.
The Studio is a generic curation tool, but its code names the classification dimensions of one domain: fixed fields in the document model, in the ingestion task, in the curation and extraction routes, and domain wording in the interface and in the generated files. ## Proposal - An instance declares its **facets** in its configuration file: `{ id, label, description?, weight? }`. None by default. - The document model, the ingestion task, the curation filters and the extraction scoring iterate over the declared facets instead of naming fields. A facet is stored as a flat list under its identifier in the front matter, so existing documents stay valid for an instance that declares the same identifiers. - The interface shows the declared facets and uses neutral wording. - `AGENTS.md`, the README and the sample configuration stop describing one domain as the product. ## Out of scope - Facets suggested by the AI extraction: the extraction adapter has a fixed output schema. - Facets per tenant: they come with the per-tenant resources. ## Acceptance - Unit tests on the reading of facets, the document properties, the filters and the scoring. - No domain term left in `src/`.
Sign in to join this conversation.
No labels
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
modaka/studio#24
No description provided.