Skip to content

feat: hard-code VA3LM GeoVision across Zyra + EYERIS Foundry bridge - #44

Merged
sonoxo merged 30 commits into
mainfrom
feature/va3lm-geovision
Aug 26, 2026
Merged

feat: hard-code VA3LM GeoVision across Zyra + EYERIS Foundry bridge#44
sonoxo merged 30 commits into
mainfrom
feature/va3lm-geovision

Conversation

@sonoxo

@sonoxo sonoxo commented Aug 26, 2026

Copy link
Copy Markdown
Owner

VA3LM GeoVision

Promotes the existing VIRGINIA/VAL3M live-implementation stack into the hard-coded VA3LM geospatial visual-intelligence control plane.

Implemented

  • /VA3LM
  • canonical /VA3LM-PALANTIRVABRAIN3LM-GPT-DOUG-LLM-ZYRA-XUNA-SONOXO-ECOSYSTEM
  • GEOVISION STATUS
  • GEOVISION CAMERAS <ontology>
  • GEOVISION DETECTIONS <ontology>
  • /api/va3lm/geovision/status
  • EYERIS_BASE_URL detector-health bridge
  • EYERIS_ONTOLOGY default Ontology binding
  • Camera/Detection reads through the existing Foundry Ontology API gateway
  • environment contract and beginner runtime docs
  • dedicated Zyra Live Implement CI on the VA3LM branch

This PR also carries forward the previously built /RICHMONDVA3LM graceful shutdown and VZN 8088 implementation work that continued on the feature branch after the original VAL3M PR merged.

Verified

Dedicated run 33024439601 passed npm install, npm test, and npm 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 optional EYERIS_BASE_URL.

sonoxo added 30 commits August 26, 2026 18:17
@sonoxo
sonoxo merged commit 9374520 into main Aug 26, 2026
4 checks passed

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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) => {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge 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 👍 / 👎.

Comment on lines +69 to +70
} catch (error) {
if (!String(error).includes('Reference already exists')) throw error;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge 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 👍 / 👎.

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.

1 participant