Conflict
PHP runtime constraint
Composition lists php ^8.2; earlier possible dependencies list php ^8.5.
This entry is recorded as Conflict in the Items section.
The evidence contains competing descriptions; this page does not choose a winner.
Source-qualified discovery inventory
Competing source descriptions and decisions intentionally left unresolved.
Document context
Every value below mirrors the JSON document. Friendly labels and explanations add context without replacing the exact field name or recorded value. Follow any “raw record” link to inspect or edit the same data.
schema_versionVersion of the discovery-inventory document shape.
0.1.0catalogue_statusMaturity of this catalogue data, not implementation status.
discovery_inventoryauthorityHow this document may be used and what it must not be mistaken for.
Evidence-derived inventory; not a final implementation-governing SSOT. Preserve source modality and consult conflicts.json.categoryStable subject area used to organize the inventory.
conflicts_open_questionsdescriptionHuman-language explanation preserved by the inventory.
Competing source descriptions and decisions intentionally left unresolved.Structured collection
11 top-level entries. Nested values are expanded inside each entry.
Conflict
Composition lists php ^8.2; earlier possible dependencies list php ^8.5.
This entry is recorded as Conflict in the Items section.
The evidence contains competing descriptions; this page does not choose a winner.
Conflict
Console surface says owner JWT while Sessions firmly specifies opaque hashed PostgreSQL tokens and rejects stateless JWT sessions.
This entry is recorded as Conflict in the Items section.
The evidence contains competing descriptions; this page does not choose a winner.
Conflict
Gateway says key JWT + device header + use-key constraints, whereas Key Execution Plane and request-format sources describe fixed signed requests and reject bearer Credential ID.
This entry is recorded as Conflict in the Items section.
The evidence contains competing descriptions; this page does not choose a winner.
Conflict
Public/gateway/console route grouping overlaps but is not explicitly mapped to Owner Control Plane/Key Execution Plane.
This entry is recorded as Conflict in the Items section.
The evidence contains competing descriptions; this page does not choose a winner.
Conflict
Legacy assertion/access/control field names are not explicitly mapped to Authentication/Authorship/Confidentiality purpose names.
This entry is recorded as Conflict in the Items section.
The evidence contains competing descriptions; this page does not choose a winner.
Open question
Package is listed, but Owner JWTs conflict with session rules and Key JWTs conflict with signed requests; package role/necessity is unsettled.
This entry is recorded as Open question in the Items section.
A maintainer decision or further specification is still needed.
Open question
Symfony cache/rate-limiter are listed while Redis/distributed nonce caching is deferred; adapters/storage and necessity are unspecified.
This entry is recorded as Open question in the Items section.
A maintainer decision or further specification is still needed.
Open question
Normalized path/query, byte encodings, timestamp window, nonce size/encoding details, errors, and concurrency semantics are not fully specified.
This entry is recorded as Open question in the Items section.
A maintainer decision or further specification is still needed.
Open question
Statuses, overlap/grace intervals, transition authorization, retention, and transaction boundaries are incomplete.
This entry is recorded as Open question in the Items section.
A maintainer decision or further specification is still needed.
Open question
Guzzle, CORS, validation, dotenv, Monolog, cache/rate limiter and other packages are listed without source-stated capability mapping or final status.
This entry is recorded as Open question in the Items section.
A maintainer decision or further specification is still needed.
Open question
Distinct destinations/clients/networks are recorded evidence only; IP addresses cannot prove physical separation.
This entry is recorded as Open question in the Items section.
The source states this firmly, rather than as a suggestion.