skill-node-architect-agentic-system

Designs, wires, and validates node-graph architectures for tiered autonomous agent systems.

Updated Jun 20, 2026
One-click install
npx skills add https://github.com/Noetfield-Systems/SourceA --skill skill-node-architect-agentic-system-noetfield-systems
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-node-architect-agentic-system
Source: https://github.com/Noetfield-Systems/SourceA/tree/main/.cursor/skills/skill-node-architect-agentic-system
Command: npx skills add https://github.com/Noetfield-Systems/SourceA --skill skill-node-architect-agentic-system-noetfield-systems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Autonomous agent pipelines often become fragmented collections of orphan scripts with hidden dependencies and no verifiable execution proof. This Skill enforces a single explicit graph SSOT where every node has a command vector, receipt file, typed edges, and tier placement, so multi-agent systems stay governable and auditable. ## Core Features & Use Cases - Explicit node graph design: Define nodes with snake_case ids, command vectors, receipt paths, planes (INTERNAL, RUNTIME_GLUE, HUB_API, PORTFOLIO), and typed edges (trigger, gate, wire, fan-out, data, orchestrate, surface, glue, alarm) in a versioned JSON graph. - Parallel tier orchestration: Organize nodes into T0 Safety, T1 Truth, T2 Fleet, and T3 Proof tiers that run sequentially across tiers and in parallel within tiers via a ThreadPool runner. - Change classification and proof ladder: Classify changes as G0–G3 and apply the matching validation, from graph linting to full runner execution with JSON receipts. - Use Case: When adding a new live-wire validator to an agentic system, follow Pattern A to create the script, register the graph node with edges_in/edges_out, update the directory map and mesh catalog, then run validate-pipeline-node-graph-v1.sh and the tier runner to produce a receipt. ## Quick Start Ask the agent to design and register a new node in the pipeline graph, then validate it with the graph validator and run its tier to produce a receipt.

Frequently Asked Questions about skill-node-architect-agentic-system

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

FAQPage Schema
How do I add a new node to an agentic pipeline graph?

Adding a node follows a fixed workflow: assign a snake_case id, tier, and plane, set the command vector and receipt path, declare edges_in and edges_out, then register it in the directory map and mesh catalog. Finish by running the graph validator and the tier runner to produce a JSON receipt.

What is a node graph runner with parallel tiers?

A node graph runner executes nodes organized into tiers such as T0 Safety through T3 Proof, running tiers sequentially but siblings in parallel via a ThreadPool when the tier sets parallel to true. Each node writes a receipt file, and the runner emits a graph-level receipt for verification.

Can n8n workflows be part of a node graph architecture?

Yes, n8n workflows are supported as glue nodes on the RUNTIME_GLUE plane for external cron or webhook triggers only. They must be declared in a workflow manifest and can never serve as law, brain, or SSOT nodes in the graph.

Why should pipeline scripts be registered in a graph instead of run standalone?

Orphan scripts without a graph row create fragmented pipelines that fail governance audits and lack execution proof. Graph registration gives every node typed edges, a receipt, tier placement, and validation, making the system auditable and safe to run unattended.

What are the limitations of parallel node execution in tiers?

Parallel execution is only safe within a tier when nodes do not mutate shared files such as receipts in the same directory. Nodes can declare skip_if conditions like hub_down or panic_active, and tiers remain sequential across boundaries to preserve gate ordering.