FCC Part 100 ontology: Zyra regulatory runtime binding - #53
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 03f55681ba
ℹ️ 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".
| "ontologyRef": "./fcc-space-modernization-part100.v1.json", | ||
| "project": "ZYRA", | ||
| "mode": "PRODUCT_POLICY_AND_RUNTIME_CONTEXT", |
There was a problem hiding this comment.
In the main Zyra deployment, this reference is never loaded: a repo-wide search finds no consumer for either new JSON file, while script/build.ts bundles only imports reachable from server/index.ts and Vite builds only the client root. As a result, the ontology files are absent from dist, so the declared policy guards, event types, notifications, and regulatory surfaces have no runtime effect despite this being labeled PRODUCT_POLICY_AND_RUNTIME_CONTEXT.
Useful? React with 👍 / 👎.
| {"id":"REPLY_5_DAY","trigger":"END_OF_OPPOSITION_RESPONSE_WINDOW","windowDays":5,"authority":"47_CFR_100_133_C"}, | ||
| {"id":"UNRESOLVED_60_DAY_NOTICE","trigger":"END_OF_PUBLIC_COMMENT","windowDays":60,"action":"FCC informs applicant/public of reasons preventing action if full action has not occurred","authority":"FCC_26_47"} | ||
| ], | ||
| "applicationRouting": {"GSO_SYSTEM":["FCC_FORM_312_MAIN","SCHEDULE_O_ORBITAL","SCHEDULE_F_FREQUENCY"],"NGSO_SYSTEM":["FCC_FORM_312_MAIN","SCHEDULE_O_ORBITAL","SCHEDULE_F_FREQUENCY"],"VTSS_SYSTEM":["FCC_FORM_312_MAIN","SCHEDULE_O_ORBITAL","SCHEDULE_F_FREQUENCY","SPACE_SAFETY_EVIDENCE"],"MOSS_SYSTEM":["FCC_FORM_312_MAIN","SCHEDULE_O_ORBITAL","SCHEDULE_F_FREQUENCY","COMPONENT_SYSTEM_RULESETS"],"EARTH_STATION":["FCC_FORM_312_MAIN","SCHEDULE_B_EARTH_STATION"],"NATIONWIDE_NON_SITE_EARTH_STATION":["FCC_FORM_312_MAIN","SCHEDULE_B_EARTH_STATION","SITE_REGISTRATION_AS_APPLICABLE"],"US_MARKET_ACCESS":["FCC_FORM_312_MAIN","MARKET_ACCESS_INFORMATION"]}, |
There was a problem hiding this comment.
For VTSS, MOSS, nationwide non-site earth-station, and market-access applications, this routing table emits SPACE_SAFETY_EVIDENCE, COMPONENT_SYSTEM_RULESETS, SITE_REGISTRATION_AS_APPLICABLE, and MARKET_ACCESS_INFORMATION, but none appears in the ApplicationModule vocabulary on line 12. A consumer resolving routes against the canonical module class will therefore reject or omit these requirements, producing incomplete filing-readiness results for exactly those four license classes.
Useful? React with 👍 / 👎.
| "NATIONWIDE_NON_SITE_EARTH_STATION":"A single license for one or more immovable earth stations that may operate in the United States and territories subject to applicable site registration requirements." | ||
| }, | ||
| "processingRules":[ | ||
| {"id":"COMPLETENESS_30_DAY","trigger":"FILED","targetState":"PUBLIC_NOTICE_OR_DEFICIENCY_NOTICE","windowDays":30,"authority":"FCC_26_47"}, |
There was a problem hiding this comment.
When the completeness rule runs for a filed application, it targets PUBLIC_NOTICE_OR_DEFICIENCY_NOTICE, which is not one of the declared ApplicationState values. This leaves the state-machine binding with an unrepresentable state instead of an explicit branch to the existing PUBLIC_NOTICE and DEFICIENCY_NOTICE states, so consumers that validate transitions against the ontology cannot apply this rule.
Useful? React with 👍 / 👎.
1 participant
Embeds FCC 26-47 / SB Docket 25-306 as a machine-readable Part 100 ontology and binds it to Zyra as product/runtime policy context. Adds status vocabulary, event types, provenance rules, deadline/evidence surfaces, transition tracking, and guards against inferred authorization or conflating proposed FNPRM changes with adopted rules.