docs(org): add Cognivanta engineering baseline

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,32 @@
+---
+name: Bug report
+about: Report a defect in a Cognivanta repository
+title: "[bug]: "
+labels: ["bug"]
+---
+
+## Summary
+
+What happened?
+
+## Impact
+
+What is broken and who is affected?
+
+## Steps to reproduce
+
+1.
+2.
+3.
+
+## Expected behavior
+
+## Actual behavior
+
+## Evidence
+
+Logs, screenshots, error messages, or links.
+
+## Environment
+
+Repo, branch, commit, and runtime context.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,27 @@
+---
+name: Feature request
+about: Suggest a small improvement or product change
+title: "[feat]: "
+labels: ["enhancement"]
+---
+
+## Problem
+
+What problem are we solving?
+
+## Proposed change
+
+What should change?
+
+## Business value
+
+Why does this matter?
+
+## Acceptance criteria
+
+- [ ]
+- [ ]
+
+## Notes
+
+Anything else the team should know.

PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,22 @@
+## Summary
+
+What changed?
+
+## Why
+
+Why is this needed?
+
+## Validation
+
+What did you check?
+
+## Risk
+
+What could go wrong?
+
+## Checklist
+
+- [ ] Scope is minimal
+- [ ] No secrets were added or changed
+- [ ] No production settings were changed
+- [ ] Documentation was updated when needed

README.md

@@ -124,3 +124,8 @@ The goal is not technology for its own sake, but the creation of practical syste
 ## Focus
 
 Operational Intelligence • AI-Assisted Automation • Telecom Operations • Observability • Workflow Orchestration • Infrastructure Automation • Autonomous Systems • Reliability • Analytics • Execution Systems
+
+
+## Engineering baseline
+
+- [Cognivanta engineering baseline](docs/engineering-baseline.md)

docs/engineering-baseline.md

@@ -0,0 +1,20 @@
+# Cognivanta Engineering Baseline
+
+Use this baseline for small, repeatable improvements across Cognivanta repositories.
+
+## Minimum standard
+
+- Every product repo should have a clear README.
+- Changes should go through a pull request, preferably draft until ready.
+- Add issue templates when the repo receives operational or product work.
+- Add a minimal CI check for active code repos.
+- Keep deployment instructions close to the code.
+- Avoid new dependencies unless they reduce risk or manual work.
+
+## Review rules
+
+- No secrets in code, docs, or workflow files.
+- No production changes without explicit intent.
+- Prefer the smallest change that improves clarity or reliability.
+- Document the validation command when a repo has one.
+- Keep workflows simple and readable.