issue-core/registry/capabilities/capability.infotech.issue-tracking.md
tegwick 1427d268a0
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 2s
docs(reuse): establish reviewed NetKingdom security capabilities
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a137ca-5c77-7a71-b9ae-23ad9b0b5684
2026-10-14 06:39:38 +02:00

110 lines
3.4 KiB
Markdown

---
id: capability.infotech.issue-tracking
name: External issue tracker connector
summary: CLI and Python adapters for external issue systems.
owner: issue-core
status: draft
domain: infotech
tags:
- issue-tracking
- connector
- work-record
- security
- netkingdom
- framework-reuse
maturity:
discovery:
current: D4
target: D5
confidence: high
rationale: INTENT.md, SCOPE.md, CAPABILITY-issue-tracking.yaml, mapping design,
boundary-sync policy, AGENT_INTEGRATION.md.
availability:
current: A2
target: A3
confidence: high
rationale: 'Source interface assessed 2026-10-14: CLI and Python adapters for
external issue systems. Availability describes the delivery form, not production
acceptance. Internal work originates in owner files; external projection is
optional.'
external_evidence:
completeness:
level: C2
confidence: medium
basis: scope_vs_intent_and_consumer_expectations
satisfied_expectations:
- Forgejo + local SQLite backends
- CLI with JSON output; project/map commands
- work_record_uuid optional on TaskSpec
- credential handling via env vars (FORGEJO_TOKEN preferred; GITEA_API_TOKEN deprecated
alias; ISSUE_CORE_API_KEY)
broken_expectations: []
out_of_scope_expectations:
- Fleet task origin / intake promotion (work-record canon)
- Default IssueSink for internal findings (activity-core)
reliability:
level: R1
confidence: low
basis: consumer_quality_signals
known_reliability_risks:
- manual backend configuration (auto-detect planned)
- no built-in issue locking beyond assignee+state
- inward boundary sync not shipped
discovery:
intent: CLI and Python adapters for external issue systems
includes:
- CLI and Python adapters for external issue systems
excludes:
- Internal work originates in owner files; external projection is optional
assumptions: []
use_cases:
- 'U09: Maintainer observes posture, prioritizes findings, coordinates work and
verifies outcomes'
research_memos: []
availability:
current_level: A2
target_level: A3
current_artifacts:
- README.md
target_artifacts: []
consumption_modes:
- CLI
- source
relations:
depends_on: []
supports: []
related_to:
- capability.activity.event-coordinate
- capability.security.iam-tooling-suite
evidence:
documentation:
- README.md
consumer_guidance:
recommended_for:
- Maintainer observes posture, prioritizes findings, coordinates work and verifies
outcomes
not_recommended_for:
- Internal work originates in owner files; external projection is optional
known_limitations:
- Internal work originates in owner files; external projection is optional
- 2026-10-14 architecture review estimates operational maturity separately; a registry
entry does not authorize execution or establish deployment.
---
# External issue tracker connector
CLI and Python adapters for external issue systems.
## Reuse boundary
Internal work originates in owner files; external projection is optional.
## Supported use cases
- U09: Maintainer observes posture, prioritizes findings, coordinates work and verifies outcomes
## Evidence and integration
- [README.md](../../README.md)
Assessment: CUST-WP-0081, 2026-10-14. Relations identify interfaces to compose; they do not certify native integration. Existing external evidence levels are retained where present. New entries use conservative C1/R0 until consumer assessment exists.