[AdaWorldAPI]

Records the operator's 2026-10-21 rulings on scope, ownership and coverage. This PR adds no feature code: it changes only the map, the guard and the plan.

Surface coverage (ISS-SURFACE-COVERAGE-SEMANTICS, resolved here)

• data/hubspot/surface_map.tsv gains a coverage column with five values: planned / implemented / deferred / out-of-scope / unclassified.

• surface::parse_map rejects a row whose class disagrees with its deliverable: UNPLANNED ⇔ unclassified, NONE ⇔ out-of-scope, and a D-id for planned, implemented or deferred.

• surface::check_board accepts implemented only when the D-id is Shipped on STATUS_BOARD. A Shipped D-id never makes its API count as served on its own.

• Pinned counts, 1,506 functions in total:

  class	families	functions
  implemented	0	0
  planned	109	1,161
  deferred	28	329
  out of scope	3	16
  unclassified	0	0

ISS-SURFACE-UNPLANNED (decided)

• New D-ids, added to the integration plan first, then to the board and the feature matrix:
  • D-MKT-5: marketing events, 37 functions.
  • D-EXT-1: app platform, 22 functions, deferred.
  • D-DOC-1: Files API, 19 functions.
  • D-OPS-1: tenant quotas, 9 functions.
  • D-DATA-1: versioned ingestion, 4 functions.
• Folded into existing D-ids:
  • behavioural events → D-FLOW-2, which D-QRY-6 reads;
  • tags → D-ONT-7 (definitions) and D-STO-3 (relations);
  • deal splits → D-COM-1;
  • forecasts → D-QRY-6;
  • AEO → D-MKT-4 (deferred).
• Out of scope, kept in the inventory with their reasons: partner program and API metadata, 16 functions.

D-DOC-1 is bounded to hubspo-docs over spear (plan §2.5.1)

spear main c69cacb was read and classified:

status	what
implemented	SHA-256 content store, mail ingest/placement, mailbox IAM
type only	UploadIntent, DriveScope (no user drives)
stub	Graph transport
planned, not built	DeliveryIntent, Entra resolution, delivery RBAC, receipts, activity / send_receipts
missing, not planned	document record, document reference, document authorization, folders

• D-DOC-1 is Blocked on ISS-SPEAR-DOCUMENT-CONTRACTS and on D-DELIVER-2..6. It builds no content store, version history, Graph client, authorization model or receipt model.
• The ingest, delivery and lookup flows are written down.
• No Files API operation is reported as served.

ISS-PACKED-RUN-RBAC-GRAIN (decided: option b)

Authorization is per property, keyed by the stable table ordinal and independent of the packed run. Option (c) is defense in depth, not a substitute. The contract follows in the D-IAM PR.

Verification

• cargo fmt --check, cargo clippy -D warnings and cargo test --workspace are green.
• Six disable runs turned the surface tests red:
  • agreement check off;
  • deferred pin moved;
  • unclassified accepted;
  • the shipped check off;
  • board lookup by prefix;
  • implemented accepted without a D-id.

🤖 Generated with Claude Code

https://claude.ai/code/session_01PPcakjk7ioQsnasmNDtc5z

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-21T00:34:53.452055Z	b89a6a1	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b89a6a13b3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".