CleverAgents knowledge representation layers 0-3
The root of every UKO node. Anything that can appear in an actor's context.
An information unit that contains other information units (file, module, class, section).
A leaf-level information unit (function body, paragraph, config value).
Metadata attached to another information unit (comment, docstring, attribute).
An interface point between containers (export, API endpoint, public method signature).
Parent contains child (e.g., module contains class).
Weak reference (e.g., a function mentions a type in a docstring).
Strong dependency (e.g., import, inheritance, call).
A rendered text representation of this node at a specific detail depth. Multiple renderings at different depths may exist for the same node. The depth is indicated by the associated uko:renderingDepth value.
The integer detail depth at which the associated uko:hasRendering was produced. Paired with uko:hasRendering via a blank node or reification.
Shorthand for the maximum-depth rendering of this node (complete, unabridged content). Equivalent to uko:hasRendering at the domain's maximum depth.
The CleverAgents Resource (by ULID) this node was extracted from.
Path within the resource (e.g., file path relative to the resource root).
Byte or line range within the source file (e.g., '42:1-87:0').
Links a revised node to its predecessor.
A source code module (file, package, namespace).
Any callable unit (function, method, procedure, lambda).
A type or schema definition (class, struct, interface, enum, typedef).
Links a test case to the callable it tests.
A complete document (article, report, manual, specification).
A top-level division of a document (e.g., Part I, Part II).
A numbered or titled section within a chapter.
A subsection nested within a section (arbitrary depth).
An inline code listing or example within a document.
A figure, diagram, or image with an optional caption.
A tabular data element within a document.
An editorial comment or annotation (e.g., HTML comment, review note).
The document's table of contents -- an interface into the document's structure.
A glossary of terms defined in the document.
Semantic relationship: this unit discusses a topic that is the subject of another unit.
This unit cites a bibliographic reference.
Explicit cross-reference (e.g., 'see Section 3.2').
Reading order: this unit comes before the target unit.
The nesting depth of this section (1 = top-level, 2 = subsection, etc.).
Word count of the text content in this unit.
Natural language of the document (e.g., 'en', 'fr').
JSON-encoded list of topic keywords extracted from this unit.
A database schema (namespace for tables, views, etc.).
A database view (virtual table defined by a query).
A stored procedure or function in the database.
A column or table constraint (NOT NULL, UNIQUE, CHECK, etc.).
A database index on one or more columns.
A COMMENT ON COLUMN annotation in the database.
A foreign key constraint -- an interface point between tables.
A database-level API endpoint (e.g., PostgREST, GraphQL).
Foreign key relationship from this column to a column in another table.
This view's query references columns from the target table.
This stored procedure reads from or writes to the target table.
This trigger fires on events on the target table.
This migration modifies the schema of the target table.
SQL data type (e.g., 'VARCHAR(255)', 'INTEGER', 'JSONB').
Estimated row count from database statistics.
The SQL/PL body of the stored procedure.
A configuration block or section (e.g., a YAML map, TOML table).
A deployment unit (e.g., Kubernetes Deployment, Docker Compose service).
A network endpoint (HTTP route, gRPC service, message queue).
This service connects to or depends on the target service.
This service exposes the target endpoint.
An OO class that contains methods and attributes.
A type class defining a set of operations for types.
A monadic type encapsulating computation context.
A header file defining exported declarations.