Skip to content

[v0.2] Rebaseline AGENTS.md for WrightKit repository ownership #141

Description

@Teakowa

Release coordination: #135
Architecture dependency: #136
Terminology cleanup: #140
Protocol contract: language-provider-protocol#1

Goal

Update the root AGENTS.md as a concise repo-local operating guide for Wright inside the multi-repository WrightKit ecosystem.

Scope

  • Reframe Wright around tooling/orchestration ownership rather than durable ownership of OPY/DEL compiler internals or canonical Workshop semantics.
  • Route work to the semantic/product owner before editing:
    • canonical Workshop semantics/catalog/WIR -> workshop-rs;
    • source-language semantics/compiler internals -> the owning provider repo;
    • provider protocol contract -> language-provider-protocol;
    • tooling/orchestration/integration/generic edit safety -> Wright.
  • Update the architecture-boundary guidance after [v0.2] Rebaseline language ownership and licensing boundaries #136 is accepted.
  • Distinguish current migration state from accepted target architecture.
  • Preserve valid operational guidance on issue scope, role authority, provenance, regression evidence, focused diffs, worktrees, and safe delivery.
  • Verify any remaining commands/crate paths against the repository and remove stale routing guidance.
  • Point to authoritative roadmap/ADR/protocol docs rather than duplicating them.

Non-goals

  • Defining the architecture inside AGENTS.md.
  • Moving compiler/core code.
  • Creating organization-level agent instructions.
  • Editing provider-repository agent guides from this issue.

Acceptance criteria

  • Root AGENTS.md describes Wright as the WrightKit tooling/orchestration repository.
  • Repository selection clearly distinguishes Wright, workshop-rs, LPP, and provider-owned work.
  • Current implementation and target ownership are not conflated during migration.
  • The document stays concise, repo-local, and backed by accepted architecture/protocol sources.
  • No new internal phase-number roadmap terminology is introduced.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions