Skip to main content

Office repository-context projection

Status​

Interface contract for one-way repository context from the GitHub estate into Office.

Purpose​

Allow Office to enrich operational fronts with repository identity/readiness context without making the GitHub estate aware of, or authoritative over, Office front identity or Carry State.

Direction​

projects repository estate
  repo_id -> repository context
               |
               v
Office Front Registry
  front_id + optional repo_ids[]
               |
               v
Office compile enrichment

The direction is intentionally one-way. projects never consumes front_id, Carry State, Office priority, or execution posture to produce this projection.

Producer contract​

Artifact: context:github-repositories@1

The artifact is keyed only by stable estate repo_id values. Minimal shape:

{
  "contract": "context:github-repositories@1",
  "generated_at": "2026-09-01T00:00:00Z",
  "repositories": {
    "repo.example": {
      "github": "owner/repository",
      "lifecycle": "active",
      "readiness": "ready",
      "observed_at": "2026-08-31T23:00:00Z"
    }
  }
}

Fields beyond github are optional projections of estate-owned semantics/observations. Consumers must tolerate missing or unknown fields.

Consumer contract​

Office may associate a front with zero or more stable repo_id values. That relationship belongs to Office/front metadata, not to projects.

Office may use repository context to:

  • show repository links;
  • flag stale/unknown readiness context;
  • prepare support or maintenance briefs;
  • provide execution evidence pointers.

Office must not automatically change Carry State, horizon, priority, or Principal escalation from repository context unless an explicit Office rule declares that consequence.

Independence invariants​

  1. front_id never appears in the producer artifact.
  2. repo_id never becomes the Office front identity.
  3. A front with no repositories remains valid and compilable.
  4. Missing repository context is advisory/unknown, not a compile failure by default.
  5. A repository may be referenced by several fronts without duplication in the producer artifact.
  6. projects remains read-only with respect to Office state.

Migration note​

This contract creates the seam required before repository-health semantics or implementation move out of office-auto-lab. It does not itself move Repo Health runtime code.