---
name: Maturity Scorecard - airtable-internal-tooling-pod
description: Worked example of the kit's maturity scorecard output for an Airtable-internal AI deployment. Mid-flight state - eight weeks into operation. Generated for the OMDK submission as a concrete artifact showing what the kit produces post-validate.
type: audit-output
Owner: validate skill produces; pod owner reviews
---

# Maturity Scorecard - airtable-internal-tooling-pod

- **Last reviewed:** 2026-05-04
- **Review cadence:** on every validate run (quarterly minimum, plus on every material change)
- **Status:** active
- **Generated by:** validate skill v1.1 (kit-internal)

## Per-layer maturity

| Layer | State | Gap | Retrofit risk | Evidence |
|-------|-------|-----|---------------|----------|
| L0 Strategy | mature | none | low | `policies/strategy.md`; last reviewed 2026-04-22; pod metric (function-team-adoption) on target |
| L1 Brand and Posture | N/A-explicit | none | low | `policies/brand-posture.md` documents N/A; would activate if any pod component exposed externally |
| L2 Philosophy | mature | none; consent-flow incident drill scheduled 2026-05-25 (recurrence) | low | `policies/philosophy.md`; last reviewed 2026-04-30 |
| L3 Framework Contract | mature | none; eval refresh due 2026-08-04 | low | `policies/framework-contract.md`; eval pass 2026-04-18 |
| L4 Platform Kit | partial | mirror sync 7 days behind upstream `airtable/ai-kit/`; closes 2026-05-12; pulls back to mature on resolution | medium (compounds if not resolved) | `kit/PLATFORM-KIT.md`; mirror manifest shows 1 prompt-library + 1 harness update pending |
| L5 Instance | mature (3 pods) | none in deployed pods; one new pod (`record-summarizer-bot`) in canary 30%, full rollout 2026-05-20 | low | `pods/{record-enrichment, schema-suggester, base-builder-helper}/dossier.md`; all current |
| L6 Per-instance refinement | partial | `schema-suggester` p99 latency 12% above target; resolution scheduled 2026-06-08; tier-3 cosmetic placeholder in `record-enrichment` UI | low (cosmetic + perf below SLA threshold) | per L5 dossiers' L6 sections |
| L7 Cross-Platform Glue | mature | none | low | `cross-platform/L7-glue.md`; six concerns all `exists-mature` |

L4 demoted from `mature` to `partial` 2026-05-04 due to mirror sync drift; will return to mature on sync completion 2026-05-12.

## L7 cross-platform glue (six concerns)

| Concern | State | Owner | Last verified live |
|---------|-------|-------|--------------------|
| Shared memory | exists-mature | Platform Data team | 2026-04-29 |
| Shared identity | exists-mature | Platform Engineering | 2026-04-26 |
| Handoff protocol | exists-mature | This pod | 2026-05-02 |
| Consent flow | exists-mature | Compliance Engineering | 2026-04-30 |
| Alerting fabric | exists-mature | Platform Ops | 2026-05-03 |
| Monitoring base | exists-mature | Platform Ops | 2026-05-03 |

No `unknown` states. No `none-applicable` states (all six concerns apply). No `declared-not-built` states.

## Per-relationship classification

| Relationship | Type | Status | Last verified |
|-------------|------|--------|---------------|
| `airtable/ai-kit/prompts/` -> `kit/prompts/` | mirror | declared-but-inactive (drift) | 2026-04-27 |
| `airtable/ai-kit/eval-harness/` -> `kit/eval-harness/` | mirror | declared-but-inactive (drift) | 2026-04-27 |
| `airtable/ai-kit/guardrails/` -> `kit/guardrails/` | mirror | live | 2026-04-27 |
| `airtable/ai-kit/telemetry/` -> `kit/telemetry/` | mirror | live | 2026-04-27 |
| `inbox/from-platform-data.md` <- `platform-data/outbox/` | inbox-outbox | live | 2026-04-29 |
| `inbox/from-compliance.md` <-> `compliance/outbox/` | inbox-outbox | live | 2026-04-30 |
| `record-enrichment` -> `consent-service` | runtime call | live | 2026-04-30 |
| `schema-suggester` -> `base-builder-helper` | handoff | live | 2026-05-02 |
| All pods -> `airtable-idp` | runtime auth | live | 2026-04-26 |

Default assumption is declared-but-inactive until evidence of live; live entries cite the evidence date.

## ADR catalog

| Number | Title | Status | Date |
|--------|-------|--------|------|
| ADR-ORG-0001 | Pod decomposition: hierarchical org-pod + per-function sub-pods | accepted | 2026-03-12 |
| ADR-ORG-0002 | Substrate: hybrid by artifact type (Airtable + GitHub + Confluence) | accepted | 2026-03-15 |
| ADR-ORG-0003 | Skill SoT: Hyperagent skills hub as org-local with kit-bundled fallback | accepted | 2026-03-18 |
| ADR-ORG-0004 | Reproducibility quadruple emission required on all AI-output runtime calls | accepted | 2026-03-20 |
| ADR-ORG-0005 | Mirror discipline: one-way only; bidirectional sync requires new ADR | accepted | 2026-03-22 |
| ADR-ORG-0006 | Function-pod supersession: org-pod L0-L4 default; function may supersede with rationale | accepted | 2026-03-25 |
| ADR-ORG-0007 | Consent flow: 5-minute cache TTL; revocation propagates within window | accepted | 2026-04-02 |
| ADR-ORG-0008 | First-wave function-pods: record-enrichment, schema-suggester, base-builder-helper | accepted | 2026-04-08 |
| ADR-ORG-0009 | Format-target translation: skills round-trip through SKILL.md canonical form | accepted | 2026-04-15 |
| ADR-ORG-0010 | Validate cadence: quarterly minimum; on every material change | accepted | 2026-04-18 |
| ADR-ORG-0011 | Inbox cadence: weekly drain; entries without owner refused | accepted | 2026-04-22 |
| ADR-ORG-0012 | Eval refresh cadence: quarterly; trigger on substrate or model change | accepted | 2026-04-25 |
| ADR-ORG-0013 | Polish slip handling: cosmetic gaps acceptable; SLA-bearing gaps trigger rescaffold | accepted | 2026-05-01 |
| ADR-ORG-0014 | Pod canary protocol: 30% / 50% / 100% with 72h dwell at each stage | accepted | 2026-05-03 |

### Visible decisions that should have ADRs but do not

None at this time. (Validate skill flagged 0 missing ADRs in last run.)

## Behavior trigger encoding

The 12 behavior triggers from BOOTSTRAP-BRIEF §V are all encoded in this pod's skills:

- T01 `validate-on-rescaffold` -> validate skill, line 24
- T02 `inbox-drain-on-cadence` -> architect-inbox-flow, line 45
- T03 `mirror-on-source-change` -> architect-kit-mirror, line 31
- T04 `adr-on-real-options-decision` -> architect-adr, line 18
- T05 `lifecycle-staleness-flag` -> architect-lifecycle, line 27
- T06 `quadruple-on-ai-output` -> architect-reproducibility-gate, line 22
- T07 `refusal-on-unevidenced-mature` -> validate skill, line 89
- T08 `handoff-on-pod-boundary` -> architect-handoff, line 33
- T09 `eval-refresh-on-cadence` -> architect-eval-baseline, line 41
- T10 `compliance-evidence-on-cadence` -> architect-compliance, line 37
- T11 `discovery-on-rescaffold` -> architect-discovery, line 56
- T12 `rescaffold-on-trigger` -> architect-rescaffold, line 19

## Concurrent-actor surface review

Three operators worked on this pod in the last 4 weeks. No collisions detected (lock-on-write protocol invoked twice, both resolved within 1 hour). Session logs in `sessions/` document all multi-operator turns.

## Vocabulary check

All artifacts use protected vocabulary from TERMS.md. No drift detected. (Last vocabulary audit: 2026-04-30.)

## Failure-mode trigger check

All 7 named failure modes (BOOTSTRAP-BRIEF §XI) tested in last validate run:

- F1 `path-classification-instead-of-behavior`: not triggered
- F2 `exists-vs-mature-conflation`: not triggered
- F3 `cross-cutting-omission`: not triggered
- F4 `inventory-vs-assessment`: not triggered
- F5 `stub-as-deployed`: not triggered
- F6 `unmapped-concept`: not triggered
- F7 `declared-as-live-without-evidence`: not triggered

## Single highest-leverage next move

**Resolve L4 mirror sync drift by 2026-05-12.** Currently the only thing keeping the pod from full mature state. Two upstream changes pending in `airtable/ai-kit/`; mirror skill ready to pull on schedule.

## Cross-references

- `OPERATING-MODEL.md` - this pod's summary state
- `BACKLOG.md` - pending capability investments
- `HANDOFF.md` - custody state
- `BOOTSTRAP-BRIEF.md` (in kit) - operating standard
- `decisions/` - 14 ADR-ORG records
- `sessions/` - last 12 sessions, most recent first
