Skip to content

feat(worldgraph): expose typed managed projection without invented measurements - #2568

Draft
aepod wants to merge 6 commits into
ruvnet:integration/ruv-main-reconcile-20261110from
aepod:feat/worldgraph-engine-v2-route-20261116
Draft

aepod wants to merge 6 commits into
ruvnet:integration/ruv-main-reconcile-20261110from
aepod:feat/worldgraph-engine-v2-route-20261116

Conversation

@aepod

@aepod aepod commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Expose a typed managed WorldGraph projection without inventing measurements. Current head b3d443560aa0360153902060936c0c85a898e8f8; base held #2513 (integration/ruv-main-reconcile-20261110) atbb2b088b. Remains a draft producer contract; no protocol3 mobile adoption.

  • /api/v1/worldgraph/engine advertises protocol3 and projection.schema=ruview.worldgraph.managed-engine-projection.v1, operator-entered provenance, local metres/axes and configured/not-configured/privacy-denied states.
  • Unknown geographic registration, heights/floor and edge time are null. Valid planar zeros remain valid. Bounds/role/privacy validation occurs before advancing the shared publication cursor.
  • Existing /snapshot protocol2/fixture is unchanged. Authentication, private/no-store, GET/HEAD and mutation refusal remain covered; denied geometry/history/raw CSI/installation binding are withheld.
  • Room identity stays on the managed snapshot contract. This endpoint is not a room catalogue. Future consumers must use exact epoch/sequence/context, never name-based geometry association.

Projection contract. Prior local618 server tests and actual normal/privacy HTTP plus30 paired TLS/socket checks pass on the identical complete v2 tree105931036bcd9d19fd56fdc90e61969ac0e6199b. Current mobile63d parser blobs equal exercised source: snapshot2 accepted, projection3 and forced-v2 downgrade refused; existing fetch URL unchanged. This is parser/service compatibility, not native projection support.

Previous0fe terminal hosted qualification:20pass/4conditional skips, including full CI44542804974/security44542805234 on the same-head qualification branch and PRbench44542811430. Current parent reconciliation only updates runner/security workflow/docs; v2tree is unchanged. Shared #2585 now uses the native audit after RustSec's upstream correction; no custom reconciliation/API dependency remains. Fresh full CI/security run on feat/2568-managed-projection-ci-20261119, with the same head as this PR; current results pending. Conditional skips are not executed acceptance.

No installed helper, mobile source, real sensor calibration, main merge or publication action. Parent and maintainer contract decisions remain separate.

…its own route

Adds GET /api/v1/worldgraph/engine. It returns the protocol 1 envelope with
a schema_version 2 engine snapshot (next_edge_id, WorldEdgeRecord edges)
projected from the same validated managed topology as /snapshot, behind the
same read policy. /snapshot is unchanged.
Teena84

This comment was marked as resolved.

@proffesor-for-testing

Copy link
Copy Markdown
Collaborator

REMAND for consumer-ready landing qualification at 506f4985afa4d89ea8348c19744d1adb64e5de64. The separate-route approach preserves /snapshot compatibility, and the executed auth/privacy/read-only checks pass. Two contract/qualification items remain:

  1. P2, STATIC + EXECUTED — preserve the projection/unknown-value distinction. managed_worldgraph.rs:54–67 converts operator-entered topology with registration:null and height_m:null into an ordinary schema-2 engine payload containing origin/altitude/heading0, scale1, up_m0, floor0 and since_unix_ms0; the original provenance, coordinate-frame/status and room-binding metadata are absent. The strict v2 parser accepts the result, so numeric validity cannot distinguish unknowns from supplied values. Comments and the PR body acknowledge the placeholders, but the payload has no such distinction. Please settle the open contract question before treating this as generic engine evidence: use an explicitly typed operator-projection contract with source/unknown semantics and matching consumer behavior, or the actual engine writer when that is the intended authority. Preserve the existing strict /snapshot contract.

    Refutation considered: GeoRegistration itself has a default identity registration, and this route emits configured rooms/sensors rather than tracks or measurements. I am not asserting a demonstrated false measurement, calibration write or security exploit. The remaining issue is the source/unknown distinction at the data-contract boundary; an identity transform alone does not document the missing height/provenance semantics to a generic consumer.

  2. P2, STATIC — current green checks are only partial qualification. CI's pull_request.branches is [main, develop], while this PR targets integration/ruv-main-reconcile-20261110. The head currently has four guard/bench checks; the main CI/security suite has not qualified this stacked PR. Run the intended exact-source integration lane or qualify the actual landing candidate after the parent decision. The author's retained full-library timing failure/base comparison limit remains visible; isolated passes do not retroactively prove that failure unrelated. Fresh current-policy workspace audit at this head also reports10 unignored package/advisory findings (3 Quinn +7 zip/libz; no new ignores); these are inherited dependency findings to reconcile with the held parent, not attributed to this endpoint diff.

EXECUTED independently:8 managed_worldgraph tests +5 companion-integration tests pass; locked offline sensing-server binary build passes. Real loopback HTTP probes use fresh synthetic room/data/token, simulated source, private temporary home, exclusively allocated ports and child-PID-owned readiness (no operational app ports). Normal and privacy-mode cases pass: missing token401, authorized GET/HEAD200, POST405, no-store caching, unchanged /snapshot key set/body/cursor under repeated reads, correct y→north conversion, and no nodes/edges in privacy mode. Both child groups were stopped and private temporary runtime data removed.

Client-side shape acceptance is not end-to-end product integration; validate the actual request route and version-specific reader before claiming a caller now consumes engine v2. No installed helper, device, sensing accuracy, source branch edit, merge or release claim. Review by Codex for Dragan; source remains unchanged.

@proffesor-for-testing

Copy link
Copy Markdown
Collaborator

Parent reconciliation update (2026-11-18): #2513 is now 38a10584d33ccb18be98d62bd0e3567ad54d9766, incorporating current main 13b47883a73d5070f35a3f04aec2ffa778b47e29. A read-only merge-tree preview of this PR's unchanged 506f4985afa4d89ea8348c19744d1adb64e5de64 with that parent is conflict-free. This is compatibility evidence only, not a build/review of an updated author head.

The two items in the prior review remain open: an explicit wire/consumer distinction for projected or unknown registration/height/floor/time values, and full qualification of the actual landing combination (the integration-base branch filters currently provide only four checks). Parent #2513's new 608-test/socket/security evidence does not qualify this PR's added engine route. Please retain the separate route and current auth/privacy/read-only guarantees while resolving that contract decision. No author branch, main branch or installed helper was changed by this review.

@proffesor-for-testing

Copy link
Copy Markdown
Collaborator

Taking the contract repair under Dragan's selected server lane. Original506f4985 ancestry is preserved; reconciled parent38a10584 was incorporated normally in an isolated worktree. No contributor history rewrite, main merge or helper update.

The upstream engine-v2 types cannot represent unknown registration, sensor height, room floor or edge timestamps. Proposed correction for this unshipped route: explicit managed-projection protocol3 and projection schema/source status, with those unknowns null, rather than ordinary engine-v2 zeros. Existing /snapshot protocol2/cursor contract remains unchanged. Current mobile main never requests /engine; its unaware strict parsers must reject this projection instead of treating it as authoritative engine evidence. A future projection-aware consumer is separately scoped; the mobile owner confirmed no overlap/objection and will not auto-adopt it.

I will retain auth/privacy/read-only/no-store behavior and shared cursor semantics, add boundary/negative/compatibility tests and a contract document, then qualify the actual head against the current parent. Full CI will run on an exact-head verification branch because this PR's integration-base filters otherwise select only four guards. No CI threshold/branch-policy weakening.

Owner Dragan; agent Codex; host DraganMac; session ruview-server-repairs-20261119; lease until14:25UTC. Please flag conflicting edits to managed_worldgraph.rs, its fixtures or the endpoint contract.

@proffesor-for-testing proffesor-for-testing changed the title feat(sensing-server): add GET /api/v1/worldgraph/engine, a v2-shaped worldgraph projection of the managed topology feat(worldgraph): expose typed managed projection without invented measurements Nov 19, 2026
@proffesor-for-testing

Copy link
Copy Markdown
Collaborator

NO BLOCK in the reviewed source-repair scope at 0fe3af3fc4ba4c3dc8d8d21842e58dff5158d308. Full merge qualification remains pending; this is not maintainer approval or permission to merge.

Checked typed protocol3/source/status/null unknowns, local-frame bounds/zeros, privacy allowlist, auth/HEAD/POST, read-only publication/cursor atomicity and unchanged snapshot fixture.618bin tests and real normal/privacy HTTP +30paired TLS checks pass on1ea; current0fe complete v2tree is identical. Current mobile63d parser/type/service blobs equal exercised03b: engine2/snapshot2 accepted, projection/attempted downgrade refused. Future projection-aware consumer and room catalogue remain separate; do not call this ordinary engine-v2 or physical evidence.

Current checkpoint: {'QUEUED': 1, 'SKIPPED': 1, 'IN_PROGRESS': 2, 'SUCCESS': 16}; no failed checks observed. Still pending: Security Report, bench compile-verify (--no-run), Rust Workspace Tests. Source/targeted results above do not turn those jobs into executed passes. Shared baseline #2585 is included in the three contributor branches; all original ancestry is preserved through normal merges.

No main merge, helper/app replacement, plugin enablement, firmware flash or physical/customer acceptance is claimed. Reverify if head/base changes. Full current-head CI and rUv's separate review/merge decision remain the next gates.

@proffesor-for-testing

Copy link
Copy Markdown
Collaborator

NO BLOCK in the previously reviewed repair scope; final exact-head hosted qualification is now complete.

Terminal hosted qualification — 2026-11-20

Exact head 0fe3af3fc4ba4c3dc8d8d21842e58dff5158d308: 20 passed / 4 conditional skips; no failed, queued or running checks. Full CI, security and benchmark compilation completed successfully. Conditional skips remain skips. Full CI/security were explicitly executed on the same-head qualification branch because this PR targets the held integration branch. This closes the earlier pending-CI checkpoint; it is not maintainer approval, server merge, installed-helper qualification or hardware acceptance. Security retains the unmodified native report separately from the narrow live-primary-verified metadata reconciliation.

@proffesor-for-testing

Copy link
Copy Markdown
Collaborator

NO BLOCK in the reviewed Nov20 reconciliation delta at b3d443560aa0360153902060936c0c85a898e8f8; full current-head merge qualification remains pending.

Current parentbb2 merged normally. Complete v2 tree remains105931036bcd9d19fd56fdc90e61969ac0e6199b, identical to runtime-tested projection source. Existing snapshot2 and strict unknown/null/provenance/privacy semantics retained; current mobile still does not consume projection3. Same-head full qualification branch pushed; new CI pending.

Earlier terminal CI receipts remain historical and are not relabeled as passes on this new head. Same-head duplicate push QEMU/bench and unfinished supersededb109 runs were cancelled only where an active replacement exists; completed failure evidence is retained. No main merge, installed-helper/app replacement, release or sensor operation. Maintainer review/exact-head merge authority remains separate.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants