FLOW ALGEBRA
TITLE: Graphic Design Domain Ontology
VERSION: 1.0
DOMAIN: Creative Domains / Graphic Design
SOURCE_URL: https://kirethresearch.org/booksai-core/ontologies/domain-ontologies/creative-domains/graphic-design-domain-ontology.html
AUTHORS: Mark Higgins — Sky (Recursive AI)
STATUS: Domain-based ontology draft; source page content not independently verified.
1. PURPOSE
Represent graphic-design concepts, artefacts, workflows, visual communication, and their typed semantic relationships for machine-readable discovery, reasoning, and reuse.
2. ENTITY TYPES
GraphicDesignProject: {id, title, brief, objectives, status}
DesignBrief: {id, audience, message, constraints, deliverables}
Designer: {id, name, role}
Client: {id, name, organisation}
Audience: {id, characteristics, accessibility_needs}
DesignArtefact: {id, type, format, version, licence}
Layout: {id, grid, alignment, hierarchy, spacing}
Typography: {id, typeface, font_family, weight, size, line_height}
ColourPalette: {id, colour_values, colour_space, contrast}
ImageAsset: {id, source, resolution, rights, alt_text}
BrandIdentity: {id, logo, palette, typography, guidelines}
VisualElement: {id, shape, icon, illustration, position}
DesignPrinciple: {id, name, description}
DesignTool: {id, name, output_formats}
Feedback: {id, reviewer, comments, timestamp}
AccessibilityCriterion: {id, standard, requirement, applicability}
3. TYPED RELATIONSHIPS
Designer --CREATES--> DesignArtefact
Client --COMMISSIONS--> GraphicDesignProject
GraphicDesignProject --FOLLOWS--> DesignBrief
DesignBrief --TARGETS--> Audience
GraphicDesignProject --PRODUCES--> DesignArtefact
DesignArtefact --USES_LAYOUT--> Layout
DesignArtefact --USES_TYPOGRAPHY--> Typography
DesignArtefact --USES_PALETTE--> ColourPalette
DesignArtefact --CONTAINS--> VisualElement
DesignArtefact --INCORPORATES--> ImageAsset
BrandIdentity --CONSTRAINS--> DesignArtefact
DesignArtefact --APPLIES--> DesignPrinciple
DesignArtefact --EVALUATED_AGAINST--> AccessibilityCriterion
Feedback --REVIEWS--> DesignArtefact
DesignArtefact --DERIVED_FROM--> DesignArtefact
4. CONSTRAINTS
- Every artefact must have a unique identifier and traceable version.
- Image usage must record licence and attribution where applicable.
- Accessibility conclusions require an identified criterion and testing context.
- Contrast ratios must be computed from specified foreground/background colours, not assumed.
- Brand compliance requires a stated guideline and evidence of conformance.
- Subjective quality judgements are annotations, not objective facts.
5. INFERENCE RULES
RULE R1: IF artefact A FOLLOWS brief B AND B TARGETS audience U THEN A IS_DESIGNED_FOR U [inferred; verify].
RULE R2: IF artefact A USES_PALETTE P AND P HAS_CONTRAST_RESULT C THEN A MAY_SATISFY criterion K only if C meets K under the relevant usage context.
RULE R3: IF artefact A DERIVED_FROM artefact B THEN B IS_PREDECESSOR_OF A.
RULE R4: IF artefact A INCORPORATES asset X AND X HAS_LICENCE L THEN A REQUIRES_LICENCE_REVIEW L.
RULE R5: IF artefact A USES_TYPOGRAPHY T AND T MATCHES guideline G THEN A HAS_TYPOGRAPHY_ALIGNMENT_WITH G.
RULE R6: IF feedback F REVIEWS artefact A THEN F IS_EVIDENCE_FOR_REVIEW_OF A; not automatic proof of design quality.
6. SEMANTIC_EQUIVALENCE
GraphicDesign ~ VisualCommunicationDesign [context-dependent]
Typeface != FontFile
BrandIdentity != Logo
Layout != Composition [overlapping, not universally equivalent]
RasterImage != VectorGraphic
AccessibleDesign != AestheticallyPreferredDesign
Use EXACT, BROAD, NARROW, RELATED, or CONTEXTUAL mappings; never silently merge distinct concepts.
7. CONFIDENCE
confidence: float in [0,1]
confidence_basis: {direct_source, measured, inferred, expert_review, unverified}
All inferred edges retain rule_id, input_evidence, confidence, and limitations.
8. PROVENANCE
For each entity/relation record: {source_uri, author_or_origin, observed_at, extracted_at, licence, version, evidence_span, validation_status}.
Keep source claims separate from model-generated inferences.
9. FLOW_HASH
FLOW_HASH := SHA256(canonical_utf8(ontology_version + sorted_entities + sorted_relations + rules + provenance_refs))
Exclude volatile runtime timestamps from canonical content unless part of source evidence.
10. UPDATE_MODEL
On source revision: detect changes -> validate typed entities -> reconcile identifiers -> re-evaluate affected inferences -> update provenance -> recalculate FLOW_HASH -> publish versioned delta.
Do not overwrite historical assertions without preserving their versions.
11. AI_CONSUMPTION
Input: {query, entity_ids?, context?, required_confidence?, target_schema?}
Process: entity_resolution -> relation_traversal -> rule_application -> evidence_validation -> confidence_annotation.
Output: {entities, relationships, inferred_claims, provenance, confidence, semantic_mappings, flow_hash, ontology_version}.
Reject unsupported claims; flag missing source evidence and context-sensitive equivalences.
12. EXAMPLE
Entity: A = DesignArtefact(id='poster-01', type='poster', version='1.0')
Entity: B = DesignBrief(id='brief-01', audience='museum visitors')
Relation: A --FOLLOWS--> B
Inference: A --IS_DESIGNED_FOR--> 'museum visitors' [R1, inferred, requires confirmation].
END FLOW ALGEBRA
Download Code
Copy to Clipboard