feat: hard-code VA3LM GeoVision across Zyra + EYERIS Foundry bridge - #44
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9008968038
ℹ️ 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".
| catch (error) { res.status(502).json({ error: String(error) }); } | ||
| }); | ||
|
|
||
| app.post("/api/foundry/ontologies/:ontology/actions/:action/apply", async (req, res) => { |
There was a problem hiding this comment.
Require authorization before forwarding Foundry operations
When this service is reachable beyond a trusted single-user localhost and FOUNDRY_TOKEN is configured, any caller can invoke this route using the server's privileged bearer token; the unguarded /api/virginia/execute endpoint can likewise reach APPLY_ACTION and SHUTDOWN_ZYRA. Because no authentication or role check precedes these handlers, anonymous callers can read or mutate Foundry data and stop the service. Add authorization enforcement, or bind the gateway to loopback behind an authenticated proxy, before exposing these routes.
Useful? React with 👍 / 👎.
| } catch (error) { | ||
| if (!String(error).includes('Reference already exists')) throw error; |
There was a problem hiding this comment.
Reconcile an existing overlay branch before updating it
When a non-dry-run workflow is retried while the previous overlay branch still exists, this catch continues as though the branch were new. The subsequent Contents API call attempts to create the already-present SVG without its current sha, so GitHub rejects the update; if the default branch has advanced, the README update can also use a SHA that does not match the existing overlay branch. Fetch and update the branch's current files, reset the branch, or skip repositories with an existing overlay PR instead of merely swallowing this error.
Useful? React with 👍 / 👎.
VA3LM GeoVision
Promotes the existing VIRGINIA/VAL3M live-implementation stack into the hard-coded VA3LM geospatial visual-intelligence control plane.
Implemented
/VA3LM/VA3LM-PALANTIRVABRAIN3LM-GPT-DOUG-LLM-ZYRA-XUNA-SONOXO-ECOSYSTEMGEOVISION STATUSGEOVISION CAMERAS <ontology>GEOVISION DETECTIONS <ontology>/api/va3lm/geovision/statusEYERIS_BASE_URLdetector-health bridgeEYERIS_ONTOLOGYdefault Ontology bindingZyra Live ImplementCI on the VA3LM branchThis PR also carries forward the previously built
/RICHMONDVA3LMgraceful shutdown and VZN 8088 implementation work that continued on the feature branch after the original VAL3M PR merged.Verified
Dedicated run
33024439601passednpm install,npm test, andnpm run check.Capability boundary
VA3LM GeoVision is wired for authorized, non-identifying object/scene recognition. It does not add face recognition, biometric embeddings, named-person lookup, or persistent individual tracking.
Deployment boundary
Runtime wiring is implemented. Actual Foundry/EYERIS connectivity requires server-side
FOUNDRY_BASE_URL,FOUNDRY_TOKEN,EYERIS_ONTOLOGY, and optionalEYERIS_BASE_URL.