Maintainer decision, 2026-07-29: adopts TRSL V1C1 as this repo's
preliminary governing license, per target-revenue's
workplans/TREV-WP-0008-governance-and-pilot-rollout.md T05. Full
specialist legal review is deferred until out of beta (target-revenue
SCOPE.md §1). No Phase is yet declared for this repo.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Rewrite INTENT for UUIDv7+canonical identity, file-first topology, dual
lifecycles, intake+promotion findings path, and shipped vs target connector
surface. Add ISSUE-WP-0005 to implement mapping/store/CLI and close SCOPE
gaps; mark alignment-review remediation done.
Audit INTENT against the ratified work-record types standard, ADR-001, and
architecture draft §4.2. Records alignments, soft frictions, dual-lifecycle
gaps, and recommended INTENT edits; no hard north-star collisions found.
Rewrite SCOPE to separate what issue-core provides today (models, backends,
CLI, REST, sync, deploy) from in-scope growth and out-of-scope fleet work.
Align package __init__ description with the connector role.
Retarget INTENT, SCOPE, README, ROADMAP, and agent docs from "task landing
zone" to external-tracker connector per work-record canon and architecture
draft §4.2. Add UUID↔external-id mapping design; mark ISSUE-WP-0004 finished
and cross-file activity-core ACTIVITY-WP-0022 for IssueSink policy.
INTENT.md currently claims to be 'a single, observable place where tasks
land' -- exactly the landing-zone role CUST-WP-0060's founder-reviewed
architecture draft (WorkOrchestrationArchitectureDraft.md v0.2, section
4.2) assigned away from issue-core, decided while reviewing the live
incident this repo caused: activity-core's daily-todo-md-stale-review
routed through IssueSink -> issue-core -> Forgejo, producing 5 issues
nobody was meant to see (now paused).
5 tasks: rewrite INTENT.md/SCOPE.md/README/ROADMAP for the connector
framing (work records originate as repo files per ADR-001; issue-core
is the optional external-tracker projection), design (not implement)
the UUID<->external-id mapping surface, and file the activity-core-side
follow-up to fix the IssueSink default. Docs-only scope; stage-3
implementation work stays in the-custodian.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Forgejo .forgejo/workflows/publish-python-package.yml already publishes to the
Forgejo PyPI registry. CUST-WP-0059-T01.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Adds publish-forgejo and a workflow_dispatch/tag workflow so issue-core
0.2.x can be published to forgejo.coulomb.social before vergabe-teilnahme
drops Gitea lockfile URLs.
Legacy in-cluster gitea-http repos are archived (issue create 423). Route
the default ingestion backend to https://forgejo.coulomb.social with
the-custodian as the central automation task inbox.
Sync AGENTS.md, CLAUDE.md, and .claude/rules from updated project_rules
templates: workplan-first session protocol, legacy terminology footnote,
and GET /workplans/ examples.
Add supports/related_to for vergabe-teilnahme and activity-core, cite
SCOPE.md, update test count to 120 (verified), and document dual-canonical
relationship with CAPABILITY-issue-tracking.yaml.
Honest first-pass maturity vector grounded in README/docs/tests present
in this repo; no invented evidence. Flagged for human review before
publish. See reuse-surface history/2026-07-06-coverage-classification.md.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Broaden POST /issues/ so triggering_event_id is any non-empty traceability
string, enabling cron/scheduled activity-core emissions with stable keys like
"scheduled" while event-driven paths still send UUIDs. Document the railiance01
ArgoCD deployment path in docs/argocd-gitops.md and update ISSUE-WP-0003 task
status to reflect repo-side progress.
- Align agent files with on-disk workplan prefixes (infer from workplan ids)
- Set workplan domain to registered domain_slug; add topic_slug where applicable
- Repair frontmatter delimiter formatting; migrate legacy task status literals
- Regenerate AGENTS.md, CLAUDE.md, and .claude/rules from State Hub templates
Apply the new 'tooling' category (reusable internal tooling/infrastructure)
from the Repo Classification Standard. First-pass agent classification.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
First-pass agent classification per the Repo Classification Standard v1.0
(canon-repo-classification); pending human review.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Introduce Dockerfile, entrypoint, and k8s/railiance manifests for the
ArgoCD GitOps pilot (ISSUE-WP-0003). Rename the Gitea PyPI build arg to
GITEA_PYPI_INDEX_URL so pip still resolves dependencies from PyPI.
