Skip to content

[Tracking] Onboard TerraYield (Meridian) as a federation peer #14

Description

@mortonanalytics

Coordination issue (IONe side) for onboarding TerraYield / Meridian (morton-analytics-llc/eo_ag) as a federation peer on the IONe network.

Context

IONe already names TerraYield as reference peer #2 (md/design/ione-substrate.md:17, app-integration-playbook.md:5), but TerraYield has shipped none of the six peer surfaces yet (md/design/foreign-tenant-mapping.md:238, map-view.md:140). IONe v0.1 supports the generic peer path; the TerraYield-specific gaps are the identity broker and an end-to-end test.

IONe-side work

TerraYield-side work (morton-analytics-llc/eo_ag)

  • morton-analytics-llc/eo_ag#15 — reconcile the integration doc (IONe = this repo; Meridian = peer)
  • morton-analytics-llc/eo_ag#16 — P0 MCP server /mcp (anchor)
  • morton-analytics-llc/eo_ag#17 — P0 resource view-hints (ione_view)
  • morton-analytics-llc/eo_ag#18 — P0 context slice + whoami
  • morton-analytics-llc/eo_ag#19 — P1 OAuth 2.1 AS (sequence with Identity broker (S0–S7): gate for TerraYield brokered SSO #12)
  • morton-analytics-llc/eo_ag#20 — P2 signed webhook push

Sequencing

P0 (eo_ag #16–18) renders Meridian in the demo workspace with no broker dependency → unblocks #13. P1 (eo_ag #19) sequences with the identity broker (#12). Webhooks (eo_ag #20) last.


Cross-repo epic (TerraYield side): morton-analytics-llc/eo_ag#22

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestfederationIONe federation / peer integration

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions