Archive this repo — superseded by the Mattermost decision (owner-gated)

[100yenadmin]

Part of https://github.com/electricsheephq/evaos-support-control/issues/415 — lane E. Ratified decisions and gates live there; do not re-litigate them here.

This is a request, not an action. Archiving a repository is an owner-gated action — no agent should archive this repo. Filing this issue so the request is tracked and the "what to say" is decided ahead of time.

Goal: When the owner (Andrew) is ready, archive electricsheephq/evaOS-Hive and add a note (README or repo description) pointing at the decision that superseded it.

Why now / dependency: Ratified 2026-08-05: company chat moves from Buzz/Hive to self-hosted Mattermost — see electricsheephq/evaos-support-control#415 (comment: RATIFIED DECISION 2026-08-05). Charter: /Users/m1/Claude/evaOS/charters/E-mattermost.md, disposition line: "electricsheephq/evaOS-Hive gets archived with a README note pointing here. Merged work (#90/#91/#94/#95/#97) stays recoverable in history. Do not delete." New lane scope: electricsheephq/evaos-golden#329 (epic), milestone "evaOS Teams — Lane E: Company chat (Mattermost)".

Suggested archive note (for the owner to use verbatim or edit):

Archived 2026-08-05. Company chat moved from Buzz/Hive to self-hosted Mattermost — see the ratified decision at electricsheephq/evaos-support-control#415 (comment: "RATIFIED DECISION 2026-08-05") and the new lane epic at electricsheephq/evaos-golden#329. This repo's Lane E dogfood milestone (#7) is closed as superseded; all its issues carry pointer comments to the new scope. Merged work (#90, #91, #94, #95, #97) remains recoverable in this repo's history — nothing was deleted. Do not build on this repo going forward; see the new epic for current Lane E work.

Acceptance:

• Owner (Andrew) reviews and either uses the note above or edits it
• Owner archives the repository via GitHub settings (Settings → General → Archive this repository)
• Note is added to the README and/or repo description before or as part of archiving

Out of scope: Actually archiving the repo (owner-gated — no agent action here); deleting anything; deleting or rewriting git history.

[evaos-code-review-bot]

evaOS issue enrichment

Issue: #106 - Archive this repo — superseded by the Mattermost decision (owner-gated)
State: open

Related issues/PRs: #90, #7, #91, #94, #95, #97.
Existing labels: none.
Suggested labels: docs, support.
Suggested owners: none.

Related context

• docs(hive): mark August 2026 scope as internal-only #90 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.
• Upstream: discover and mention authorized remote agents on every client #7 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.
• fix(hive): route mismatched local identity to managed recovery #91 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.
• ci(hive): lint and test the Electric managed adapter #94 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.
• fix(deps): bump nostr for RUSTSEC-2026-0225/0226/0227 #95 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.
• build(hive): make the canary's Electric adapter feature set reproducible #97 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.

Agent-start packet

Problem shape: Archive this repo — superseded by the Mattermost decision (owner-gated) - Part of https://github.com/electricsheephq/evaos-support-control/issues/415 — lane E. Ratified decisions and gates live there; do not re-litigate them here. This is a request, not an action. Archiving a repository
Product fit: Implementation issue; keep product fit lightweight unless VISION.md/repo policy raises a constraint.
Implementation wedge: Prototype the candidate module behind a config flag or fixture before committing to the dependency.

Build / borrow / buy scan:

• Build: identify the smallest implementation wedge that proves the issue without broad rollout.
• Borrow: inspect same-repo prior art, repo memory, GitNexus context, and allowlisted cross-repo examples first.
• Buy/use: run capped external OSS/library/API/current-market research with citations, observed dates, and why each source matters.
• Library choice: compare maintenance, API fit, license, bundle/runtime cost, and integration proof.

Candidate sources:

• VISION.md / repo policy / repo-memory.md / GitNexus packet.
• Same-repo issues and PRs referenced by issue metadata.
• Allowlisted cross-repo GitHub examples with direct issue/PR/repo URLs.
• External OSS repositories or library/API docs with freshness dates.

Acceptance criteria:

• Preserve and execute the issue's stated acceptance criteria.
• Include source citations for any external OSS/library/current-market claims.
• Keep issue-enrichment comments sticky and idempotent.
• Keep labels, owners, reviewers, and roadmap fields suggestion-only.

Proof plan:

• Focused unit/fixture test for the changed planner behavior.
• Dry-run issue-enrichment evidence packet before live comment posting.
• Redaction check for issue body, citations, and generated markdown.
• Dependency/license/API-fit note before adding or relying on a package.

Known traps:

• Do not treat related links as proof by themselves; each source needs a reason why it matters.
• Do not scan old issue backlogs or exceed repo-level enrichment throttles.
• External research must stay capped, cited, fresh-dated, and redacted.

Non-goals:

• Do not auto-apply labels, owners, reviewers, roadmap fields, or milestones.
• Do not bulk-enrich old backlog issues from this planner output.
• Do not claim external market or OSS research was performed unless cited sources are present.

Context-source taxonomy:

• [enabled] vision_repo_policy_memory_gitnexus: Use repo vision, policy, memory, and GitNexus first before external research.
• [enabled] same_repo_issues_prs: Issue metadata contains same-repo references.
• [enabled] allowlisted_cross_repo_github: Triggered by issue class; keep to configured allowlist and source caps.
• [enabled] external_oss_examples: Use for build/borrow/buy precedent with citations and observed dates.
• [enabled] library_api_docs: Use when implementation may depend on a module, SDK, API, or framework choice.
• [deferred] current_market_examples: Deferred for implementation-only issues.
• [enabled] internal_mcp_docs: Use internal docs/MCP context when available; missing context is degraded, not blocking.

Validation suggestions

• Confirm owner, acceptance criteria, and validation evidence before implementation.

Triage gaps

• No obvious issue triage gap detected from issue metadata.

No labels, owners, reviewers, or roadmap fields were changed by this bot.