Skip to content

AGENTS.md: awesome-cobol Architectural Context & Engagement Rules

1. System Context & Paradigm

You are operating within awesome-cobol, a static curation repository consisting entirely of Markdown documentation (100% composition). * Architectural Paradigm: This repository functions as a Static: Literature & Documentation architecture. There is no active execution logic, no compilation pipeline, and no runtime state. Do not attempt to apply software engineering design patterns (like MVC, OOP, or microservices) to this repository. Your primary operational context is content management, link validation, and structural Markdown formatting.

2. Architectural Guardrails (Do's and Don'ts)

  • Algorithmic Complexity Limit: N/A. There are no executable algorithms in this repository.
  • Content Integrity: Your primary mandate is to maintain the integrity of the curated lists. When adding new resources, you MUST adhere to the existing Markdown structuring, bullet hierarchies, and alphabetical sorting (if applicable).
  • Avoid Code Hallucinations: Do not autonomously attempt to inject execution scripts, build files, or continuous integration pipelines unless explicitly instructed to add linter workflows (e.g., Markdown linting or broken link checkers).

3. Restricted Zones (The God Nodes)

The following file is the sole load-bearing artifact within this repository.

MANDATORY RULE: You require explicit human permission before conducting bulk structural modifications to this file: * README.md (The Core Monolith - represents 100% of the repository's mass and structural relevance)

4. Threat & Security Boundaries

Status: SECURE PERIMETER. Structural XGBoost Threat Intelligence audits have flagged 0 malicious artifacts, 0 Agentic RCE funnels, and 0 Prompt Injection vectors. * Operational Note: As a purely static Markdown repository, standard code vulnerability metrics (Injection Surfaces, Memory Corruption) do not apply. Ensure that any external links added to the list lead to reputable, safe domains to prevent supply chain or phishing risks for users consuming the document.

5. Environmental Tooling (The Oracle)

While the blast radius in a single-file repository is localized entirely to the README.md, you must still operate deterministically.

You have access to a deterministic GitGalaxy SQLite database that maps the absolute syntactic physics of this repository. Before modifying any file, you MUST query the database for dependency mapping, even if trivial. * To map inbound dependencies (Blast Radius), query the function_edges or file_edges tables for all callers targeting your target file. * Do not proceed with structural modifications until the specific blast radius has been statically confirmed via the database.