Skip to content

[epic] FBC channel schema with explicit semver support and simple edge mechanics #1351

Open
@grokspawn

Description

@grokspawn

Current FBC schema express the full range of what olmv0 needs to express, but we can evolve schemas to create simpler and more powerful experiences for operator authors.

(There are separate concerns for v0 and v1, so this proposal is specifically constrained to v1.

  1. write RFC (on its face, this looks not big enough for a brief)

Metadata

Metadata

Assignees

No one assigned

    Labels

    epiclifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.triage/needs-informationIndicates an issue needs more information in order to work on it.

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions