Skip to content

docs: add spec docs for environment module - #1

Merged
alexgwolff merged 18 commits into
devfrom
docs/starting-spec-envoriment
Sep 28, 2026
Merged

alexgwolff merged 18 commits into
devfrom
docs/starting-spec-envoriment

Conversation

@alexgwolff

@alexgwolff alexgwolff commented Sep 19, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Adds the first real set of module docs (README, intent, specs, and acceptance
scenarios) for src/environment/src/env_var, and refines the documentation
convention in docs/README.md based on applying it.

What does this pull request change?

  • env_var module docs (src/environment/src/env_var/):
    • README.md: module overview (sources, declarations, resolution, projection).
    • docs/env-var-intent.md: problem, intent, principles (static declarations,
      security access, explicit projection), and boundaries.
    • Specs and acceptance scenarios for four areas: declarations, resolution,
      projection, and host mappings.
  • Documentation convention (docs/README.md, docs/example/):
    • Module README layout gains an ## Overview section (free-form, detailed).
    • Spec layout: requirement statements go in a text block; the Intent link
      is listed first.
  • Requirements are written in EARS with "the software" as subject
    (The software SHALL …, WHEN … THE SOFTWARE SHALL …).
  • Minor: BUILDING.md wording ("front-matter"), root README.md reflow,
    trailing newline in .gitignore.

How to test?

  • Docs only; no code changes.
  • Open the env_var docs on GitHub and check that links between README, intent,
    specs, and acceptance files resolve (including #…-req-…/#…-acc-… anchors).

Other Notes and Links

  • All requirements and scenarios are Doc status: Draft; verification status
    is Unknown until scenarios are linked to tests.

Signed-off-by: Alex G. Wolff 13754094+alexgwolff@users.noreply.github.com

Signed-off-by: Alex G. Wolff <13754094+alexgwolff@users.noreply.github.com>
Signed-off-by: Alex G. Wolff <13754094+alexgwolff@users.noreply.github.com>
Signed-off-by: Alex G. Wolff <13754094+alexgwolff@users.noreply.github.com>
Signed-off-by: Alex G. Wolff <13754094+alexgwolff@users.noreply.github.com>
Signed-off-by: Alex G. Wolff <13754094+alexgwolff@users.noreply.github.com>
@alexgwolff
alexgwolff marked this pull request as ready for review September 23, 2026 00:40
Remove SPECIFICATIONS.md from being ignored

Signed-off-by: Alex Godoy Wolff <13754094+alexgwolff@users.noreply.github.com>
@alexgwolff alexgwolff changed the title docs: add spec pattern and docs for environment module docs: add spec docs for environment module Sep 25, 2026
alexgwolff and others added 10 commits September 26, 2026 13:27
Signed-off-by: Alex G. Wolff <13754094+alexgwolff@users.noreply.github.com>
Wrap requirement statements in text blocks and list the Intent link
first, matching docs/README.md and the example spec.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011uc2KL8jgKVwgzomc6Wdmp
Replace standalone SHALL/MAY/SHALL NOT labels with full EARS sentences
whose subject is the software, move inline conditions into WHEN clauses,
and nest Principles under the Intent section.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011uc2KL8jgKVwgzomc6Wdmp
Signed-off-by: Alex G. Wolff <13754094+alexgwolff@users.noreply.github.com>
Signed-off-by: Alex G. Wolff <13754094+alexgwolff@users.noreply.github.com>
Markdown is not rendered inside text code blocks, so the bold markers
showed up as literal asterisks.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011uc2KL8jgKVwgzomc6Wdmp
Signed-off-by: Alex Godoy Wolff <13754094+alexgwolff@users.noreply.github.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011uc2KL8jgKVwgzomc6Wdmp
@alexgwolff
alexgwolff merged commit d8c2656 into dev Sep 28, 2026
2 checks passed
@alexgwolff
alexgwolff deleted the docs/starting-spec-envoriment branch September 28, 2026 19:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants