Objective
Implement the approved Publisher Services and Distribution Configuration design across Thoth, thoth-app, thoth-dissemination and cc-license with additive schema, explicit authorization, audited migration, comparison-mode cutover, bounded pilots, monitoring and rollback.
Immutable authority at foundation review head
The Publisher Services design requires one fresh task branch and one PR per task. There is no long-lived feature/publisher-services integration branch.
Synchronization guard
Before applying this replacement: re-fetch the complete live issue body; re-fetch its current updatedAt; compare both exactly against the reviewed baseline updatedAt: 2026-07-24T17:17:09Z and body. If either the live body or updatedAt differs, do not write. Regenerate the minimal diff from the new live body, obtain fresh independent review, and obtain separate explicit CTO authorization before writing. Any later rollback must likewise re-fetch and compare the live body and updatedAt, preserve unrelated edits, and apply only a reviewed minimal reversal under explicit CTO authorization; it must never restore an old complete snapshot blindly.
Current gate
No production implementation begins before the applicable gate passes.
Tasks
Foundation
Backend
Migration and interfaces
Cutover and downstream services
Stabilization
P0-01 closure records completion of the engineering-control foundation only. It does not approve an ADR, approve the final inventory, satisfy branch readiness, or make another task ready.
Do not close a task at PR creation or CI success. Close only after independent approval, merge, required rollout/observation and repository tracker update.
Objective
Implement the approved Publisher Services and Distribution Configuration design across Thoth, thoth-app, thoth-dissemination and cc-license with additive schema, explicit authorization, audited migration, comparison-mode cutover, bounded pilots, monitoring and rollback.
Immutable authority at foundation review head
3The Publisher Services design requires one fresh task branch and one PR per task. There is no long-lived
feature/publisher-servicesintegration branch.Synchronization guard
Before applying this replacement: re-fetch the complete live issue body; re-fetch its current
updatedAt; compare both exactly against the reviewed baselineupdatedAt: 2026-07-24T17:17:09Zand body. If either the live body orupdatedAtdiffers, do not write. Regenerate the minimal diff from the new live body, obtain fresh independent review, and obtain separate explicit CTO authorization before writing. Any later rollback must likewise re-fetch and compare the live body andupdatedAt, preserve unrelated edits, and apply only a reviewed minimal reversal under explicit CTO authorization; it must never restore an old complete snapshot blindly.Current gate
No production implementation begins before the applicable gate passes.
Tasks
Foundation
Backend
Migration and interfaces
Cutover and downstream services
Stabilization
P0-01 closure records completion of the engineering-control foundation only. It does not approve an ADR, approve the final inventory, satisfy branch readiness, or make another task ready.
Do not close a task at PR creation or CI success. Close only after independent approval, merge, required rollout/observation and repository tracker update.