Repository navigation
Add read-only Forge API and Live Map /api/events feed - #2
Merged
Merged
Conversation
A stdlib WSGI app serves objects, history, links, neighborhoods and search from the ontology store, plus /api/events in the envelope Live Map already reads. A shared conformance fixture pins the feed shape; tests reproduce it on SQLite and PostgreSQL. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GcagdBzPRAWDhhc9Yipm4d
Zacharon
marked this pull request as ready for review
October 19, 2026 05:09
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Before: the ontology store could only be read from Python, and nothing connected it to Live Map.
After:
osint-forge-api --db forge.db(or--database-url postgresql://...) serves the store over HTTP. Routes are/objects,/events,/claims,/assessments,/search, plus history, links and neighborhood for each object. It also serves/api/events, a public feed in the envelope Live Map already reads (events,canonicalEvents,generatedAt,filters,sourceStatus, ...). That lets Live Map point at Forge without changing its client.The API is read-only. Writes still go through the Python store until authentication exists.
How: the API is a stdlib WSGI app with no new dependencies.
osint_forge/api/projection.pymirrors Live Map'screateNormalizedEventandtoLegacyEvent:confidenceis stored as 0..1 and published as 0..100.(0, 0)stays a mapped point.public: falseare never published.tests/fixtures/contracts/live_map_events.jsonis a shared conformance fixture. It contains fixture objects, a fixed clock, the exact expected envelope, and a type schema. The tests reproduce it on SQLite, and the CI postgres job reproduces it on PostgreSQL. Live Map can validate its own responses against the same schema. Errors come back as structured JSON with no stack traces, and provenancemetadatais not served. Details are indocs/API.md.Tests:
python -m unittest discover -s testsgives 120 OK (13 skipped without PostgreSQL). Ontology and API tests also pass against a local PostgreSQL 16.Generated by Claude Code