Skip to content

docs: retire the stale "Where this is headed" federation forecast on extend-existing-systems #257

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
os-bill merged 1 commit into from
Sep 2, 2026
Merged

docs: retire the stale "Where this is headed" federation forecast on extend-existing-systems #257

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 0 additions & 9 deletions content/docs/extend-existing-systems.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,15 +74,6 @@ Once the tables are modeled as objects bound to your existing database:
- **One permission model.** The boundary that applies to humans applies
identically to AI traffic.

## Where this is headed

The flow above works today with shipped building blocks. A richer,
**turn-key federation** experience — one-step schema import, externally
owned schema binding, and built-in safety gates — is in active design
under [ADR-0015](https://github.com/objectstack-ai/objectstack/blob/main/docs/adr/0015-external-datasource-federation.md)
(status: *Proposed*). Until it lands, the documented path — connect,
model, bind, query — is the supported way to extend an existing system.

## Start here

- [Data Sources](/docs/configure/data-sources) — connect a database, bind objects, route queries
Expand Down