slug: graphite-com
provider: Graphite
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 2
edges:
- tag: Stacks
  spec_file: graphite-com-stacks-api-openapi.yml
  capability_id: BC-4200.40
  capability_id_l1: BC-4200
  capability_name: Software Construction Management
  confidence: 0.8
  evidence: POST /stacks/branches createBranch 'Create a stacked branch'; POST /stacks/submit 'Submit
    a stack to GitHub'; schemas Branch, PullRequest
  reason: Operations create branches, submit stacked pull requests and sync with the remote — source-control
    and code-review practice, i.e. Software Construction Management. Not a release/deployment pipeline,
    so BC-4210 is not the fit.
- tag: Merge Queue
  spec_file: graphite-com-merge-queue-api-openapi.yml
  capability_id: BC-4200.40
  capability_id_l1: BC-4200
  capability_name: Software Construction Management
  confidence: 0.72
  evidence: POST /stacks/merge  mergeStack  Merge a stack of pull requests
  reason: Merging stacked pull requests is source-control and code-review practice, i.e. Software Construction
    Management. Some ambiguity with Continuous Integration Management since the vendor's merge queue 'batches
    and tests PRs in parallel', so confidence is moderate.