Recover operator approvals for STAR-RESEARCH-012/029/030/032 #157

Open
opened 2026-08-27 14:34:53 +00:00 by lost-rob0t · 0 comments
lost-rob0t commented 2026-08-27 14:34:53 +00:00 (Migrated from github.com)

Operator approval recovery

The canonical approval migration currently shows these research nodes as PENDING, but the operator has explicitly re-confirmed approval during the 2026-08-27 research review.

Approved:

  • STAR-RESEARCH-012 — corroboration-aware deduplication. Decision: if two or more sources say the same thing, StarIntel keeps one copy of the fact but remembers every source that reported it. Further research may expand lineage/source-independence handling without revoking this direction.
  • STAR-RESEARCH-029 — distributed target lease and fencing semantics.
  • STAR-RESEARCH-030 — backend-neutral KV lease store.
  • STAR-RESEARCH-032 — authenticated target-lease HTTP and execution enforcement.

Required repository correction

  • Set canonical research approval metadata to APPROVED with approval_actor: operator and evidence pointing to this operator decision.
  • Update the Research conclusion row in each Approval Table to APPROVED.
  • Add a 2026-08-27 changelog entry explaining that the canonical state was repaired after the approval-metadata migration failed to preserve the prior human decision.
  • Do not treat this as a new implementation approval or redesign; it restores the research conclusion state.
  • Keep the research-refresh work in #156 separate: additional passes can modernize assumptions while preserving the approved conclusion unless the operator explicitly supersedes/rejects it.

This issue itself is the durable operator-decision evidence for the repaired approval metadata.

## Operator approval recovery The canonical approval migration currently shows these research nodes as `PENDING`, but the operator has explicitly re-confirmed approval during the 2026-08-27 research review. Approved: - `STAR-RESEARCH-012` — corroboration-aware deduplication. Decision: if two or more sources say the same thing, StarIntel keeps one copy of the fact but remembers every source that reported it. Further research may expand lineage/source-independence handling without revoking this direction. - `STAR-RESEARCH-029` — distributed target lease and fencing semantics. - `STAR-RESEARCH-030` — backend-neutral KV lease store. - `STAR-RESEARCH-032` — authenticated target-lease HTTP and execution enforcement. ## Required repository correction - Set canonical research approval metadata to `APPROVED` with `approval_actor: operator` and evidence pointing to this operator decision. - Update the Research conclusion row in each Approval Table to `APPROVED`. - Add a 2026-08-27 changelog entry explaining that the canonical state was repaired after the approval-metadata migration failed to preserve the prior human decision. - Do not treat this as a new implementation approval or redesign; it restores the research conclusion state. - Keep the research-refresh work in #156 separate: additional passes can modernize assumptions while preserving the approved conclusion unless the operator explicitly supersedes/rejects it. This issue itself is the durable operator-decision evidence for the repaired approval metadata.
Sign in to join this conversation.
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
nsaspy/starintel-auto-research#157
No description provided.