Skip to content

docs(process): harness pin 0.34.0 -> 0.52.1 and owner decision D25 (owner list, Budget, data policy) - #328

Merged
egerev merged 5 commits into
mainfrom
process/harness-d25-0.52
Oct 28, 2026
Merged

egerev merged 5 commits into
mainfrom
process/harness-d25-0.52

Conversation

@egerev

@egerev egerev commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

Adopts harness 0.52.x / owner decision D25 in DeedKit (inbox 20261027-1900, steps 1 and 4).

  1. Pinned copy: docs/harness/{process,reviews,tiden,orchestration,skills}.md and VERSION copied verbatim from egerev/agent-harness v0.52.0 (0719ec7) by bin/pin-refresh.sh, then VERSION to v0.52.1 (81e4d3d changes no pinned rule file). Tiden CLI pin unchanged (0.42.0, same sha256), so the CI install steps read the same values.
  2. AGENTS.md: Harness values gain the data-policy document (docs/DATA-POLICY.md) and Budget: EUR 50/month without asking, monthly-cancellable spend only (owner D25 via harness). Section 1: deploys only via production.py; other production changes follow the section 2 gates (was: all production changes only via production.py; SSH "approved steps" -> section 2-gated steps). Section 2 quotes D25 as the authority (owner keeps only the five items) and maps item 2 to DATA-POLICY.md, item 3 to the Budget line, and the live actions to items 4-5: they keep section 1's exact confirmation. The autoloop Override is unchanged.
  3. docs/DATA-POLICY.md (new, from templates/DATA-POLICY.md): first version from SECURITY.md, BACKUP.md, MEDIA_STORAGE.md, ENRICHMENT.md, TELEMETRY.md and the decision log; status draft: it covers nothing until the orchestrator records the owner's one confirmation (a user-data ask); lines without an owner decision are marked proposal; the 10-25 cold-deletion request is stated as requested, not current behaviour (BACKUP_R2.md:444-454, story 516).

Owner's words: harness D25 (2026-10-27), verbatim «1) да 2)да 3)да» to the five-item owner list, the EUR 50/month cap and agent cleanup.
Change path: OWNER (AGENTS.md section 2 and harness process.md sections 1-3 text; D25 as the owner's words; pinned-copy refresh)
Local checks: no code changed; pinned files byte-compared with git -C ~/agent-harness show v0.52.1:<file>; AGENTS.md 665 words (budget 1,000).
Review record: r1 Astra (gpt-6-astra): CHANGES, 1 blocking (unconfirmed policy operative), 2 major (cold deletion vs BACKUP_R2.md; egress missed feedback readers and webhook headers), 1 minor (docs/DATA-POLICY.md not in autoloop protected paths). Fixed in c70652a. r2 scoped recheck Sol (gpt-6.1-sol xhigh): APPROVE, findings 1-3 fixed; the minor deferred as a follow-up card candidate (acceptable while the draft covers nothing).
Model: claude-opus-5-5 high

🤖 Generated with Claude Code

Copied verbatim from egerev/agent-harness v0.52.0 (0719ec7296c7fba230132e5f8af1dc30f85a71a7).

Signed-off-by: egerev <egor@gosync.ai>
Harness v0.52.1 (81e4d3d) changes no pinned rule file; only VERSION and the pointers.

Signed-off-by: egerev <egor@gosync.ai>
…policy document

AGENTS.md sections 1-2 quote owner decision D25 (harness, 2026-10-27, «1) да 2)да 3)да»): the owner keeps only the five harness items; production changes other than deploys follow the harness section 2 gates; live actions keep the owner's exact confirmation. Harness values gain the data-policy document (docs/DATA-POLICY.md, first version from SECURITY.md, BACKUP.md, MEDIA_STORAGE.md and the decision log) and the EUR 50/month Budget line. The Process line moves to 0.52.1.

Signed-off-by: egerev <egor@gosync.ai>
…s current cold deletion; full egress list (Astra r1)

Signed-off-by: egerev <egor@gosync.ai>
@egerev
egerev marked this pull request as ready for review October 28, 2026 01:16
@egerev
egerev enabled auto-merge October 28, 2026 01:17
…vent body)

Signed-off-by: egerev <egor@gosync.ai>
@egerev
egerev added this pull request to the merge queue Oct 28, 2026
Merged via the queue into main with commit 5b1edeb Oct 28, 2026
20 checks passed
@egerev
egerev deleted the process/harness-d25-0.52 branch October 28, 2026 01:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant