Skip to content

Latest commit

 

History

History
112 lines (80 loc) · 4.5 KB

File metadata and controls

112 lines (80 loc) · 4.5 KB

AffineScript Documentation Directory

This directory contains all project documentation organized by purpose.

Structure

docs/
├── README.adoc               # This file
├── specs/                    # Language specifications
│   ├── affinescript-spec.md  # Complete language specification
│   └── SPEC.adoc             # Core specification
├── governance/               # Community and process docs
│   ├── CODE_OF_CONDUCT.md    # Community standards
│   ├── CONTRIBUTING.adoc     # How to contribute
│   ├── MAINTAINERS.adoc      # Project maintainers
│   └── SECURITY.md           # Security policy
├── standards/                # Design & planning docs
│   ├── ROADMAP.md            # Development roadmap
│   ├── DECISIONS.md          # Architecture decisions
│   ├── RELEASE.md            # Release procedures
│   ├── TESTING.adoc          # Test taxonomy + PR-level gates
│   ├── PANIC-ATTACK.adoc     # Security-scan policy & disposition
│   └── PALIMPSEST.adoc       # License integration
└── guides/                   # Testing and guides
    ├── TESTING-REPORT.adoc   # (RETIRED — redirects to standards/TESTING.adoc)
    └── TESTING-REPORT.scm    # (RETIRED — redirects to standards/TESTING.adoc)

Documentation Categories

Language Specifications (specs/)

For language designers and implementers.

Governance (governance/)

For contributors and community members.

Standards & Planning (standards/)

For understanding project direction and decisions.

Guides (guides/)

For testing and quality assurance.

I want to…​

…​understand AffineScript → Start with Language Specification

…​contribute code → Read Contributing Guide

…​report a security issue → Follow Security Policy

…​understand design decisions → See Architecture Decisions

…​check the roadmap → Review Roadmap

…​see test coverage → Browse Capability Matrix (live) or Testing Standards (taxonomy + gates)

Contributing to Documentation

Documentation improvements are always welcome! See Contributing Guide for:

  • Style guidelines

  • Review process

  • Documentation testing