cb.fabric-scaling-horizon

Expand Cortical Fabric scaling horizons and validate T streaming-horizon behavior.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Metta-AI/cortical --skill cb-fabric-scaling-horizon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cb.fabric-scaling-horizon
Source: https://github.com/Metta-AI/cortical/tree/main/skills/cb.fabric-scaling-horizon
Command: npx skills add https://github.com/Metta-AI/cortical --skill cb-fabric-scaling-horizon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams continue Cortical Fabric scaling work after backend closures by coordinating horizon exploration and benchmark updates across B, params, h, and graph frontiers.

Core Features & Use Cases

  • Announce at start and align on horizon scope to ensure policy and ownership consistency.
  • Rerun current-code evidence and expand one frontier or horizon check, then compare against a baseline.
  • Update the live progress document and assign an owner to track next steps and artifacts.

Quick Start

Announce Fabric scaling horizon and rerun current-code checks while expanding a chosen frontier.

Frequently Asked Questions about cb.fabric-scaling-horizon

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

FAQPage Schema
How do I maintain Cortical Fabric scaling horizons after backend changes?

You maintain Cortical Fabric scaling horizons by rerunning current-code evidence to explore B x params x h frontiers and validating T streaming-horizon behavior, which updates benchmark results and performs parity checks across frontier axes.

What is a Fabric scaling horizon parity check?

A Fabric scaling horizon parity check is a validation process that compares benchmark results across frontier axes, such as B, params, h, and graph frontiers, against a baseline to ensure consistency after backend closures.

How do I expand Fabric benchmark frontiers for ongoing scaling work?

You expand Fabric benchmark frontiers by rerunning current-code checks, selecting one frontier or horizon check to explore, and comparing the new results against an existing baseline to identify deviations or improvements in scaling behavior.

Do I need a live progress document to track Fabric horizon updates?

Yes, you need a live progress document to track Fabric horizon updates. The process requires inspecting the live progress document, recording updates, designating an owner for artifacts, and aligning on horizon scope at the start to ensure ownership consistency.

What are the limitations of extending scaling horizons across multiple frontier axes?

Extending scaling horizons across multiple frontier axes requires coordinating B, params, h, and graph frontiers simultaneously, which can complicate parity checks and baseline comparisons if backend changes are not fully closed before starting the horizon loop.