Skip to content

SUPPORT.md

Latest commit

 

History

History
45 lines (33 loc) · 1.91 KB

SUPPORT.md

File metadata and controls

45 lines (33 loc) · 1.91 KB
Raw

Support

GDS is the agent-first control plane for the example-org and example-user repository estate. Here is where to get help.

Read the docs first

  • README — the canonical model, repository layout, and how policy compiles into bundles and repository-local projections.
  • docs/ — architecture notes, contracts, and runbooks.
  • gds <command> --help — every command documents its own flags, and --json emits a versioned result envelope suitable for scripting.
  • CONTRIBUTING.md — the verification tiers and the rules that govern generated projections.

Report a vulnerability — privately

Do not open a public issue for security problems. Report suspected vulnerabilities through a private GitHub Security Advisory. See SECURITY.md for the policy and scope.

Ask a question or report a bug

Open an issue. A useful report includes:

  • the exact command you ran and its full --json output;
  • the commit SHA or release tag, and your OS and architecture;
  • what you expected instead, and whether the repository was clean;
  • the output of gds context --json and gds doctor --json when the problem involves scope resolution, policy, or projections.

Redact tokens and private paths before pasting.

Scope of support

This project is maintained by Danil Silantyev (@example-user), CEO NDDev, on a best-effort basis. There is no SLA. Well-scoped, reproducible reports and pull requests that follow the contribution rules get attention fastest.

Issues about the vendored submodules belong in their own repositories: ci-workflows and macos-ubuntu-bootstrap.