Design Agentree work-node schema and Gira identity mapping

Open
#17 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github, typescript
Domain
documentation, tooling

Research direction

Start with the parent roadmap epic in #15, then review the repository's docs/ area before drafting the design note. The document is done when it defines the work-node schema, the repo/branch/Gira ticket identity key, opencode and GitHub PR/check mappings, adapter unknowns, and the stated v1 constraints.

Written by the indexing model from the issue text.

Description

Goal

Write the first design note for Agentree's Gira-based work map model.

Scope

  • Define the work-node schema.
  • Define the common identity key: repo + branch + Gira ticket.
  • Specify how opencode session metadata maps onto work nodes.
  • Specify how GitHub PR/check evidence maps onto work nodes.
  • List unknowns for Codex/Claude read-only adapters.

Acceptance Criteria

  • A repo doc exists under docs/ describing the schema and mapping.
  • The doc references #15 as the parent roadmap epic.
  • The doc keeps v1 opencode-native and does not require universal harness control.

Parent

Part of #15.

Dominant language
TypeScript
Stars
0
Forks
0
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from StatPan/agentree

All issues in StatPan/agentree

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.