Your business written down
In a file your people and your AI share. Edit it on a canvas or in Git: it is the same file.
- 29 kinds
- JSON Schema 2020-12
- CEL expressions
- EUPL-1.2
It is the same file.
apiVersion: gluon/v1kind: LinkTypemetadata: {name: SupplierHoldsContract}spec: semantics: association from: {type: party.Supplier, role: supplier, multiplicity: "1"} to: {type: Contract, role: contracts, multiplicity: "0..*"} backing: {kind: foreignKey, holder: to, property: supplierId} onDelete: {from: restrict}In the file: SupplierHoldsContract, lines 3, 6 and 7.
On the canvas: the same link, the line from Supplier to Contract.
Figures that are true of GOL and the designer, each with where to check it.
29 kinds, each with its JSON Schema
From Package and Domain to Skill, Query and ExtractionProfile.
GOL language guide1 file, on the canvas and in Git
The designer is an editor for GOL files, never a second model. Comments and key order survive either way.
Explore the ontology canvas2 approvals before anything is published
Its owner and security approve every change, and every approval is on record.
Review, approve and merge a proposal0 published versions changed by a miner
gluon-miner submits GOL with status proposed and its provenance. It never writes to a published version.
Ontology builder
Your business is written down once, in GOL: the Domains, Objects, Links and Actions it talks about. Every change is a proposal with a diff, and each team gets exactly the version deployed to it.
Proposals
Nothing reaches your people before its owner and security approved it.
Proposals
A visual diff on the canvas and in the files, with conflicts shown.
Approvals
The owner and security approve before anything is published.
Versions
Signed and immutable, exported and imported as signed packages.
Rollout
Staged, with shadow stages and gates, rollback and a kill switch.
A mined type,
edited before it is accepted.
apiVersion: gluon/v1kind: ObjectTypemetadata: name: Warranty plural: Warranties status: proposed # mined, awaiting reviewNote 1 description: A supplier's promise to repair or replace delivered goods. owners: ["team:procurement-data"]Note 2 provenance:Note 3 origin: mined agent: swarm/[email protected] confidence: 0.87 evidence: - {source: "source:erp-contracts", locator: row 17} - {source: "source:sharepoint-legal", locator: p.9} review: {state: pending}spec: identity: {primaryKey: [warrantyId], title: title} properties: warrantyId: {type: uuid, required: true, immutable: true} title: {type: string, required: true}Removed line: months: integerAdded line: months: {type: integer, required: true}Note 4- Proposed, never publishedA mined type arrives with status proposed and its provenance. A miner never writes to a published version.
- Its owner approvesIts owner and security approve every change, and every approval is on record.
- With its evidenceSuggestions arrive with their evidence: the source, and where in it.
- Edited before it is acceptedEdit, accept, merge or accept in bulk. Here a reviewer makes months required before accepting.
Only reviewed knowledge
reaches your people.
Mined suggestions and the review inbox put a person between a source and the model. A document that tries to give instructions is flagged.
01Ontology builder
Suggestions mined from your sources.
A mining run proposes types and links from your sources. You check each one and send it to review.
02Review inbox
Only reviewed knowledge reaches your people.
Suggestions arrive with their evidence. Edit, accept, merge or accept in bulk; a document that tries to give instructions is flagged.
03Proposals
Changes with their consequences.
Each proposal shows a diff on the canvas and in the files, with approvals, conflicts and a shadow scorecard, before you publish.
04Approvals
Nothing merges before its owner approves.
A proposal waits at its approval gate until the owner and security have signed. Every approval is on record.
Who sees which version.
Rolled out in stages, with a kill switch.
A five-step wizard with gates, rollout and rollback. Versions are signed and can be exported as packages and imported elsewhere with the signature checked.
Canvas or Git
The designer is an editor for GOL files, never a second model. Comments and key order survive either way.
An open language
The language, the decision point and the ontology builder are open source, under EUPL-1.2. The repository opens with the public release.
Where it is used
Questions
Do we have to use the designer?
No. GOL is YAML in files you keep in Git. The designer is an editor for the same files, never a second model.
Who approves a change?
Its owner and security, before it is published. Every approval is on record.
Can a team get a different version?
Yes. Each group, department or team gets exactly the version deployed to it.
Do we start from a blank canvas?
No. gluon-miner reads your sources through the mining contract and proposes types and links, each with its evidence, for review.