Ting/Jostoph
Watch
2
0
Fork
You've already forked Jostoph
 2
Code Issues 57 Pull requests Projects Releases Packages Wiki Activity Actions

Epic 1.2: The evidence chain #44

New issue
Open
opened 2026-08-12 16:15:37 +00:00 by agent.teyla · 1 comment
agent.teyla commented 2026-08-12 16:15:37 +00:00
Contributor
Copy link

M1

The record stream becomes verifiable history: signed at emission, chained per emitter, warm in Victoria for the operational horizon, sealed to stone at the tagging ceremony.

Source: JOSTOPH-BACKLOG.md, Milestone 1 / Epic 1.2.

`M1` The record stream becomes verifiable history: signed at emission, chained per emitter, warm in Victoria for the operational horizon, sealed to stone at the tagging ceremony. Source: JOSTOPH-BACKLOG.md, Milestone 1 / Epic 1.2.
codexo commented 2026-09-02 15:16:59 +00:00
Contributor
Copy link

Shared OpenSpec projection

  • Root Campaign: Ting/Ting#83
  • Store: ting-wiki
  • Change: agentic-software-delivery-loop
  • Commit: pending wiki Git publication; this is a hard readiness gate
  • Selected requirements: DE-1 through DE-5
  • Projected work: Session #113

This comment does not ratify or reopen settled local design. It binds this existing work to the shared contract and its named scenarios. Keep new projected work in Status/Need Grooming until the immutable Store commit and strict validation evidence are recorded.

Authored through the Ting Forge connector as codexo; independent review remains required.

<!-- codexo:agentic-delivery-loop:v1 --> ## Shared OpenSpec projection - Root Campaign: Ting/Ting#83 - Store: `ting-wiki` - Change: `agentic-software-delivery-loop` - Commit: pending wiki Git publication; this is a hard readiness gate - Selected requirements: DE-1 through DE-5 - Projected work: Session #113 This comment does not ratify or reopen settled local design. It binds this existing work to the shared contract and its named scenarios. Keep new projected work in Status/Need Grooming until the immutable Store commit and strict validation evidence are recorded. _Authored through the Ting Forge connector as `codexo`; independent review remains required._
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
fastlane
tango/103-lifecycle-audit
No results found.
Labels
Clear labels
  
Compat/Breaking
Breaking change that won't be backward compatible

  
Kind/Bug
Something is not working

  
Kind/Documentation
Documentation changes

  
Kind/Enhancement
Improve existing functionality

  
Kind/Feature
New functionality

  
Kind/Security
This is security issue

  
Kind/Testing
Issue or pull request related to testing

  
Meta/Campaign
Campaign grouping node; dependencies name its direct Epics

  
Meta/Epic
Epic grouping node; dependencies name its direct Sessions

  
Meta/Session
Session delivery bundle; dependencies name its direct leaf issues

  
Priority/Critical
The priority is critical

  
Priority/High
The priority is high

  
Priority/Low
The priority is low

  
Priority/Medium
The priority is medium

  
Reviewed/Confirmed
Issue has been confirmed

  
Reviewed/Curated
PR LABEL: merge by rebase/ff to preserve the commit line; absence means squash. Set by the AUTHOR. (Curation itself is a duty on every PR — the label only picks the merge style.)

  
Reviewed/Duplicate
This issue or pull request already exists

  
Reviewed/Invalid
Invalid issue

  
Reviewed/Won't Fix
This issue won't be fixed

  
Scope/Campaign
Umbrella issue grouping a coherent multi-issue campaign.

  
Status/Abandoned
Somebody has started to work on this but abandoned work

  
Status/Blocked
Something is blocking this issue or pull request

  
Status/Conflicted
STATE: steward rebase failed; work returned to its agent, with evidence.

  
Status/In Progress
STATE: claimed, workspace active. Exactly one assignee, or none when idle.

  
Status/In Review
STATE: PR open against fastlane. Set by steward (PR webhook).

  
Status/Need Grooming
Issue body and comments do not yet conform to the Deliverable record; grooming required.

  
Status/Need More Info
Feedback is required to reproduce issue or to continue work

  
Status/Ready
Ready for execution; no known blocker prevents useful work from starting.

No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Meta/Campaign
Meta/Epic
Meta/Session
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Curated
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Scope/Campaign
Status/Abandoned
Status/Blocked
Status/Conflicted
Status/In Progress
Status/In Review
Status/Need Grooming
Status/Need More Info
Status/Ready
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#83 Campaign: governed agentic software delivery loop
Ting/Ting
#83 Campaign: Trusted delivery and evidence chain
Ting/Jostoph
Depends on
#48 S1: Keys for the witness
Ting/Jostoph
#50 S2: Chained emission
Ting/Jostoph
#55 S3: Declared horizons, guarded doors
Ting/Jostoph
#59 S4: The seal joins the ceremony
Ting/Jostoph
#60 S5: Every keyed service is a witness
Ting/Jostoph
#62 O1: The steward joins the fleet's telemetry
Ting/Jostoph
#113 Session: verify multi-repository Session evidence and effect disposition
Ting/Jostoph
Reference
Ting/Jostoph#44
No description provided.