Research: define a five-signature self-hosting functional kernel - #1
Merged
Conversation
Signed-off-by: Cem Pehlivan <203530888+cemphlvn@users.noreply.github.com>
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
1 participant
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.
Summary
Proposes the minimum callable surface for OSIL to count as an ecosystem under its own interoperability model.
The research note argues that five observable semantic roles are sufficient:
parseresolverealizeprojectpreserveIt then derives optimization, composition, rendering, execution, and search as policy/implementation layers rather than additional semantic primitives.
The key proposed invariant is SELF-APPLICATION: OSIL should not claim an interoperability property for foreign ecosystems that it exempts its own native representation from demonstrating.
This PR is intentionally non-normative and only adds a research note. A later normative PR could register OSIL itself under
registry/entries/osil.yaml, add the ecosystem profile triad, and require an OSIL→OSIL round-trip conformance gate.MIT / DCO sign-off included in the commit.