Status: pre-meeting boundary
Prepared: July 28, 2026
Decision meeting: August 5, 2026
This audit prevents proposed Linked Art 1.1 terms from entering Meta Museum
contracts before their names, domains, ranges, and endpoint placement are final.
The executable source of truth is
`LINKED_ART_1_1_COMPATIBILITY_BOUNDARY` in `src/utils/linked-art.ts`.
Current boundary
| State | Terms and patterns | Current behavior |
|---|---|---|
| Supported | `added_member_by`, `removed_member_by`; auction/lot/purchase separation; exemplar-level Set provenance | Preserved by current contracts and covered by regression fixtures. |
| Candidate vocabulary/profile | possibly/probably attribution terms; brief/full response profiles | Existing implementation can demonstrate the behavior, but final 1.1 names remain pending. |
| Candidate properties | `erased_by`, `distinct_from`, `used_object_of_type`, `top_concept_of`, `Name.created_by`, `overlaps_with`, `portrayed`, `ascribed_dimension` | Not added to endpoint allowlists before the community decision. |
| Candidate classes | `Erasure`, `Portrayal` | Not mapped to a core endpoint before final class constraints are published. |
| Deferred | `AuditoryWork`, `InteractiveWork`, `Fund`, `TKLabel`, `Phase` | Source information may be retained, but no local endpoint class or proprietary substitute is introduced. |
`Name.created_by` is listed as a candidate because nested source structures are
currently preserved without a Name-specific 1.1 schema gate. Preservation must
not be described as normative support until the accepted constraint is recorded.
Verified behavior
The compatibility regression suite proves that:
- Every audited term has one unique decision state.
- Pending properties remain outside their proposed endpoint-family allowlists.
- Pending and deferred classes remain outside the core endpoint map.
- The active terms-ontology member lifecycle inverses remain accepted.
The candidate fixture pack also proves that current storage and inspection
preserve `Name.created_by`, Removal, Joining, and Leaving structures without
promoting their pending 1.1 constraints into the normative endpoint profile.
Run:
pnpm exec tsx --test tests/quality/linked-art-1-1-compatibility-boundary.test.ts
Post-meeting procedure
For each accepted term:
- Record the issue resolution, final spelling, domain, range, context URI, and
target release in the agenda tracker and reference ledger.
- Change its decision state from `candidate` to `supported`.
- Add only the required endpoint or nested-structure allowlist entry.
- Add a positive fixture and retain a negative fixture for invalid placement.
- Run the compatibility, agenda-fixture, route, documentation, and schema suites.
Deferred or unresolved terms must remain gated.
August 20 post-meeting refresh
The local `v1.1` reference checkout still matches upstream commit
`fded7e715dcbe7642b6658151a616153dacf84a0`; the branch itself has not changed
since the August 19 briefing. The issue record has changed:
the affected thing. Meta Museum may document its existing member-side fixture,
but inverse names and the related PartAddition request in #771 remain open.
digital file-level object—the unique digital copy carrying `access_point`—not
the higher-level information object shared across systems.
equivalence between concepts from distinctness between individuals, so no
proposed negative property is exported.
(required demographic/occupation vocabulary metatypes) are watch items. They
do not change a local contract until the community records a decision.
- Issue #366 now records a 1.1 agreement to put adding/removing relationships on
- Issue #524 remains open. The post-meeting clarification scopes erasure to the
- Issue #637 remains unresolved. The live discussion distinguishes negative
- New milestone issues #804 (embedded works versus references) and #806
Issue #637 now has an
internal confirmed-negative reconciliation contract(negative-reconciliation-contract.md).
It preserves curator, evidence, timestamp, rationale, and score provenance while
withholding any negative Linked Art projection. Automated `no-link` outcomes
remain unresolved candidates rather than confirmed assertions.
Issue #362 now has a
provisional response-profile contract(response-profile-contract.md). It
defines bounded server-side `brief` and `full` behavior while keeping those
labels internal until the community settles the final profile mechanism.