pogls geometry

Document POGLS V3.8/V3.9 architecture rules, constants, and design decisions.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/M111ON/POGLS4 --skill pogls-geometry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pogls geometry
Source: https://github.com/M111ON/POGLS4/tree/main/docs
Command: npx skills add https://github.com/M111ON/POGLS4 --skill pogls-geometry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

POGLS geometry provides authoritative guidance on the POGLS architecture, constants, and rules for V3.8/V3.9 to support consistent development, quick reviews, and informed decision-making across modules.

Core Features & Use Cases

  • Authoritative Core Law & sacred numbers reference for V3.8/V3.9 (162 nodes, 18/54/972, PHI constants)
  • Architecture guidance for ShellN, Delta lanes, Hydra scheduler, Rewind, Fractal gate, Temporal bridge, engine bridge, and related components
  • Review and onboarding helper to align new code with POGLS design rules and safe defaults

Quick Start

Ask me to summarize a V3.8/V3.9 rule or generate a compliant integration plan for a POGLS module.

Frequently Asked Questions about pogls geometry

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

FAQPage Schema
What are the POGLS architecture rules for V3.8 and V3.9 module development?

POGLS architecture rules for V3.8/V3.9 define core laws, sacred numbers like 162 nodes, and PHI addressing constants to guide consistent design and reviews across modules like ShellN and Delta lanes.

How do I align new code with POGLS design rules during a review?

To align new code with POGLS design rules, verify reference accuracy, ensure consistency with the Core Law, and validate conformance to sacred numbers and PHI addressing constants during architectural reviews.

Does the Hydra scheduler require specific PHI addressing constants for integration?

The Hydra scheduler integration requires strict conformance to POGLS sacred numbers and PHI addressing constants to maintain architectural consistency across the V3.8 and V3.9 system design.

What is the best way to generate a compliant integration plan for a Fractal Gate module?

The best way to generate a compliant Fractal Gate integration plan is to articulate the specific POGLS architecture rules and safe defaults documented for the V3.8/V3.9 environment.

When do I need to apply POGLS sacred numbers like 18, 54, and 972 in my architecture?

You need to apply POGLS sacred numbers like 18, 54, and 972 whenever making design decisions for modules like ShellN or Temporal Bridge to ensure reference accuracy and Core Law consistency.