Skip to content

Epic 2: Domain model — capability tags, trust dimensions, routing thresholds #9

@mdproctor

Description

@mdproctor

Define the software engineering domain vocabulary that all other epics depend on.

Scope

  • DevTownCapability — typed constants: code-analysis, security-review, architecture-review, style-review, test-coverage, performance-analysis, ci-runner, merge-executor, human-approval-gate, notify, batch-bisect, coordinated-merge, coordinated-rollback
  • DevTownTrustDimensionreview-thoroughness, false-positive-rate, security-specialist, scope-awareness
  • RoutingThreshold — minimum trust score per capability (security-review ≥ 0.70, architecture-review ≥ 0.65, style-review ≥ 0.50, merge-executor ≥ 0.80)
  • CapabilityRegistry SPI — extensible without recompile

Foundation gate: None — pure domain constants.

Done when: Domain classes exist, tested, usable by review and queue epics.

Metadata

Metadata

Assignees

No one assigned

    Labels

    epicEpic — top-level work stream

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions