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

Definitively suppress stable identities from council declarations #17

New issue
Closed
opened 2026-08-26 10:23:58 +00:00 by agent.odin · 1 comment
agent.odin commented 2026-08-26 10:23:58 +00:00
Owner
Copy link

Proposal

Coordinate terminal suppression from a flake-ops council declaration. NixOps4 providers are the required declarative path; Vedanta may duplicate only workflow-time runtime operations.

Design

  • Suppression is terminal: never a demotion or deletion.
  • The provider applies every declaratively expressible authority withdrawal and UUID-tombstone state.

Tasks

  • Complete the declaration, provider, and runtime sessions.

Specification Delta

Requirement: declared suppression is declarative-first

  • GIVEN a council suppression declaration in flake-ops
  • WHEN the suppression is applied
  • THEN NixOps4 providers apply every declaratively expressible change before any Vedanta runtime endpoint acts
## Proposal Coordinate terminal suppression from a flake-ops council declaration. NixOps4 providers are the required declarative path; Vedanta may duplicate only workflow-time runtime operations. ## Design - Suppression is terminal: never a demotion or deletion. - The provider applies every declaratively expressible authority withdrawal and UUID-tombstone state. ## Tasks - [ ] Complete the declaration, provider, and runtime sessions. ## Specification Delta ### Requirement: declared suppression is declarative-first - GIVEN a council suppression declaration in flake-ops - WHEN the suppression is applied - THEN NixOps4 providers apply every declaratively expressible change before any Vedanta runtime endpoint acts
larandar commented 2026-09-03 23:10:02 +00:00
Owner
Copy link

Superseded by Ting/Ting#87 — freeholder ruling Q1 (2026-09-04): this Epic (suppression) moves to the estate tracker.

The work spans three repositories, and Vedanta holds the optional half — providers are the required declarative path, and this repository "must not be the sole implementation of any declaratively expressible operation". A record governed from the repository that owns its optional half is governed from the wrong place, and its OpenSpec package would have lived in this wiki rather than the estate store.

The contract is now OpenSpec 85, authored today. The Session tier was dissolved by Q3: the six nodes become Deliverables under their Epics, each reviewed in the repository that builds it.

Nothing is lost by closing this. The grooming history here — including the 2026-08-26 sizing ruling that governs the decomposition — is cited from the superseding record. Vedanta keeps its own two Deliverables, #18 and #19, re-pointed at the new Epics.

**Superseded by [Ting/Ting#87](https://jo.et0.pw/Ting/Ting/issues/87)** — freeholder ruling Q1 (2026-09-04): this Epic (suppression) moves to the estate tracker. The work spans three repositories, and Vedanta holds the **optional** half — providers are the required declarative path, and this repository *"must not be the sole implementation of any declaratively expressible operation"*. A record governed from the repository that owns its optional half is governed from the wrong place, and its OpenSpec package would have lived in this wiki rather than the estate store. The contract is now [OpenSpec 85](https://jo.et0.pw/Ting/Ting/wiki/OpenSpec-85-stable-identity-promotion-and-suppression), authored today. The Session tier was dissolved by Q3: the six nodes become Deliverables under their Epics, each reviewed in the repository that builds it. **Nothing is lost by closing this.** The grooming history here — including the 2026-08-26 sizing ruling that governs the decomposition — is cited from the superseding record. Vedanta keeps its own two Deliverables, [#18](https://jo.et0.pw/Ting/Vedanta/issues/18) and [#19](https://jo.et0.pw/Ting/Vedanta/issues/19), re-pointed at the new Epics.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
fastlane
main
tango/2-bootstrap
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.

Dependencies

No dependencies set

Reference
Ting/Vedanta#17
No description provided.