skills.rest
nomeforme
nomeformeCOMMUNITY
Explore all skills by this author →
GitHub

connectome-ontology

Define the Connectome ontology, VEIL, frames, and agent architecture.

1|Updated Feb 25, 2026
Search Tags:#architecture#ontology#agents#spaces#veil#connectome#autopoietic-ai
One-click install
npx skills add https://github.com/nomeforme/connectome-monorepo --skill connectome-ontology
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: connectome-ontology
Source: https://github.com/nomeforme/connectome-monorepo/tree/main/skills/connectome-ontology
Command: npx skills add https://github.com/nomeforme/connectome-monorepo --skill connectome-ontology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Connectome ontology provides a shared semantic foundation and architectural blueprint for VEIL, agents, and spaces, unifying design decisions across the system.

Core Features & Use Cases

  • Formalizes concepts such as VEILState facets, frames, streams, and spaces to enable consistent reasoning and interoperability between components.
  • Guides cross-team development and governance by documenting interfaces, constraints, and terms used by engineers, researchers, and operators.
  • Serves as a durable reference for onboarding, reviews, and long-term maintenance, ensuring alignment around core ontology and architecture.

Quick Start

Review VEIL, frames, and agent architecture before implementing new components.

Frequently Asked Questions about connectome-ontology

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a foundational ontology for multi-agent architecture?▼

A foundational ontology for multi-agent architecture defines shared semantics, interfaces, and constraints to unify system design. It formalizes concepts like VEIL states, frames, streams, and spaces to ensure consistent reasoning and interoperability across engineering teams.

How do I standardize cross-team development for multi-agent spaces?▼

To standardize cross-team development, apply a shared architectural blueprint that documents core concepts, interfaces, and constraints. This governance approach ensures engineers, researchers, and operators maintain alignment during feature reasoning and implementation.

When do I need a formal ontology for system design?▼

You need a formal ontology for system design when establishing a durable semantic foundation for complex, multi-component environments. It anchors long-term maintenance, onboarding, and cross-team collaboration by unifying architectural decisions and risk-aware implementation.

Can I use this ontology to guide feature reasoning across streams?▼

Yes, you can use the ontology to guide feature reasoning across streams. It specifies core constraints and architectural concepts to evaluate new components, ensuring they interoperate correctly within established multi-agent spaces and VEIL states.

Does this architectural blueprint require external dependencies?▼

No, this architectural blueprint requires no external dependencies. It operates as a standalone semantic foundation designed to document interfaces and guide engineering decisions without relying on additional frameworks or external libraries.

Related Skills

Explore More Software Engineering Skills→
nesihaver-ILnesihaver-IL

create-plan

Generate a Markdown implementation plan with goals, architecture, and testing.

Community
Basic
ChegginCheggin
1

omc-reference

Expose the OMC agent catalog, tool registry, and team routing for orchestration.

Community
Intermediate
victorlouvictorlou
4

supervisor-api

Delegate agent tool looping to the Databricks Supervisor API via responses.create().

Community
Advanced
EnigmaWUEnigmaWU
1

document-architectural-decisions

Write structured 12-field Architectural Decision Records using Kruchten's decision ontology.

Community
Advanced