afyx-engineering-kit 0.0.0-stage → 0.1.0-alpha.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.afyx-source-revision +1 -0
- package/LICENSE +21 -0
- package/README.md +377 -2
- package/SECURITY.md +74 -0
- package/afyx-context/LICENSE +21 -0
- package/afyx-context/README.md +155 -0
- package/afyx-context/afyx-context.json +30 -0
- package/afyx-context/contracts/integration-v1.schema.json +34 -0
- package/afyx-context/package-lock.json +53 -0
- package/afyx-context/package.json +34 -0
- package/afyx-context/scripts/benchmark.mjs +39 -0
- package/afyx-context/scripts/build.mjs +15 -0
- package/afyx-context/scripts/comparative-benchmark.mjs +342 -0
- package/afyx-context/scripts/comparative-worker.mjs +74 -0
- package/afyx-context/scripts/graph-integration-e2e.mjs +188 -0
- package/afyx-context/scripts/integrated-dogfood.mjs +309 -0
- package/afyx-context/src/budget.js +166 -0
- package/afyx-context/src/cli.js +110 -0
- package/afyx-context/src/coordination.js +343 -0
- package/afyx-context/src/engine.js +198 -0
- package/afyx-context/src/errors.js +14 -0
- package/afyx-context/src/graph-integration-worker.js +70 -0
- package/afyx-context/src/graph-integration.js +373 -0
- package/afyx-context/src/graph-mcp-bridge.js +103 -0
- package/afyx-context/src/index.js +25 -0
- package/afyx-context/src/integrations.js +87 -0
- package/afyx-context/src/memory.js +255 -0
- package/afyx-context/src/storage.js +364 -0
- package/afyx-context/test-fixtures/coordination-worker.mjs +52 -0
- package/afyx-context/test-fixtures/graph-consumer-repo/addons/sale_extension/__init__.py +1 -0
- package/afyx-context/test-fixtures/graph-consumer-repo/addons/sale_extension/__manifest__.py +4 -0
- package/afyx-context/test-fixtures/graph-consumer-repo/addons/sale_extension/models/__init__.py +1 -0
- package/afyx-context/test-fixtures/graph-consumer-repo/addons/sale_extension/models/sale_order.py +5 -0
- package/afyx-context/test-fixtures/integrated-dogfood-repo/addons/integrated_sales/__init__.py +1 -0
- package/afyx-context/test-fixtures/integrated-dogfood-repo/addons/integrated_sales/__manifest__.py +10 -0
- package/afyx-context/test-fixtures/integrated-dogfood-repo/addons/integrated_sales/models/__init__.py +2 -0
- package/afyx-context/test-fixtures/integrated-dogfood-repo/addons/integrated_sales/models/sale_order.py +20 -0
- package/afyx-context/test-fixtures/integrated-dogfood-repo/addons/integrated_sales/models/sale_order_audit.py +11 -0
- package/afyx-context/test-fixtures/integrated-dogfood-repo/addons/integrated_sales/security/ir.model.access.csv +2 -0
- package/afyx-context/test-fixtures/integrated-dogfood-repo/addons/integrated_sales/views/sale_order_views.xml +14 -0
- package/afyx-forge/LICENSE +55 -0
- package/afyx-forge/README.md +126 -0
- package/afyx-forge/afyx-forge.json +28 -0
- package/afyx-forge/bin/afyx-forge +4 -0
- package/afyx-forge/bin/afyx-forge.cmd +3 -0
- package/afyx-forge/bin/afyx-forge.js +16 -0
- package/afyx-forge/contracts/forge-plan-v1.schema.json +172 -0
- package/afyx-forge/package.json +26 -0
- package/afyx-forge/src/classifier.js +190 -0
- package/afyx-forge/src/cli.js +111 -0
- package/afyx-forge/src/doctor.js +105 -0
- package/afyx-forge/src/guidance.js +120 -0
- package/afyx-forge/src/index.js +273 -0
- package/afyx-forge/src/planning.js +107 -0
- package/afyx-forge/src/policy.js +109 -0
- package/afyx-forge/src/workflow-refiner.js +151 -0
- package/afyx-graph/afyx-graph.json +20 -0
- package/afyx-graph/engine/LICENSE +21 -0
- package/afyx-graph/engine/README.md +104 -0
- package/afyx-graph/engine/release/RELEASE-MANIFEST.json +21 -0
- package/afyx-graph/engine/release/SHA256SUMS +2 -0
- package/afyx-graph/engine/release/afyx-graph-linux-x64.tar.gz +0 -0
- package/afyx-graph/engine/release/afyx-graph-win32-x64.zip +0 -0
- package/afyx-graph/engine/scripts/distribution-contract.mjs +212 -0
- package/afyx-graph/engine/scripts/distribution-product.json +33 -0
- package/bin/afyx-engineering-kit.mjs +61 -0
- package/install.ps1 +1053 -0
- package/install.sh +617 -0
- package/package.json +66 -4
- package/scripts/afyx-capability-orchestrator.mjs +752 -0
- package/scripts/afyx-claude-integration.mjs +547 -0
- package/scripts/afyx-context-artifact.mjs +105 -0
- package/scripts/afyx-credential-broker.mjs +75 -0
- package/scripts/afyx-doctor.ps1 +152 -0
- package/scripts/afyx-doctor.sh +146 -0
- package/scripts/afyx-forge-artifact.mjs +183 -0
- package/scripts/afyx-global-routing-policy.md +12 -0
- package/scripts/afyx-global-routing.mjs +168 -0
- package/scripts/afyx-graph-artifact.mjs +178 -0
- package/scripts/afyx-host-adapters.mjs +543 -0
- package/scripts/afyx-host-bridge-lifecycle.mjs +174 -0
- package/scripts/afyx-host-bridge.mjs +288 -0
- package/scripts/afyx-integration-contracts.mjs +825 -0
- package/scripts/afyx-mcp-integration.mjs +528 -0
- package/scripts/afyx-modular-integration.mjs +361 -0
- package/scripts/afyx-modular-runtime.mjs +451 -0
- package/scripts/afyx-native-skill-host.mjs +124 -0
- package/scripts/afyx-npm-installer.mjs +486 -0
- package/scripts/afyx-project.ps1 +205 -0
- package/scripts/afyx-project.sh +207 -0
- package/scripts/afyx-provider-backup.mjs +1206 -0
- package/scripts/afyx-provider-integration.mjs +724 -0
- package/scripts/afyx-provider-inventory.mjs +147 -0
- package/scripts/afyx-security-auditor.mjs +224 -0
- package/scripts/afyx-skill-engineering.mjs +354 -0
- package/scripts/afyx-tool-family-routing.mjs +64 -0
- package/scripts/afyx-universal-runtime.mjs +530 -0
- package/scripts/alpha_acceptance_preflight.py +240 -0
- package/scripts/benchmark-graph-memory.mjs +96 -0
- package/scripts/benchmark_capability_orchestrator.mjs +64 -0
- package/scripts/build-windows-installer.ps1 +259 -0
- package/scripts/build_forge_synthetic_image.py +328 -0
- package/scripts/check-reference-staleness.py +71 -0
- package/scripts/components.json +254 -0
- package/scripts/contracts/afyx-capability-request-v1.schema.json +189 -0
- package/scripts/contracts/afyx-capability-result-v1.schema.json +32 -0
- package/scripts/dogfood_engineering_comparison.mjs +303 -0
- package/scripts/engineering-assurance.json +28 -0
- package/scripts/install-afyx-context.ps1 +142 -0
- package/scripts/install-afyx-context.sh +126 -0
- package/scripts/install-afyx-forge.ps1 +265 -0
- package/scripts/install-afyx-forge.sh +273 -0
- package/scripts/install-afyx-graph.ps1 +571 -0
- package/scripts/install-afyx-graph.sh +438 -0
- package/scripts/install-codex-usage-tracker.ps1 +172 -0
- package/scripts/lib/AfyxComponents.psm1 +399 -0
- package/scripts/lib/AfyxSkillLifecycle.psm1 +289 -0
- package/scripts/lib/AfyxTerminal.psm1 +838 -0
- package/scripts/lib/afyx-components.sh +256 -0
- package/scripts/lib/afyx-skill-lifecycle.sh +271 -0
- package/scripts/link-global-dev.ps1 +193 -0
- package/scripts/link-global-dev.sh +130 -0
- package/scripts/phase8-paired-evidence.mjs +195 -0
- package/scripts/phase8-representative-workload.mjs +771 -0
- package/scripts/phase8-session-recorder.mjs +157 -0
- package/scripts/phase8_event_ledger.py +248 -0
- package/scripts/phase8_evidence_discovery.py +189 -0
- package/scripts/prepare-g6-package.mjs +349 -0
- package/scripts/resolve-git-release-artifacts.mjs +321 -0
- package/scripts/stage-npm-release.mjs +94 -0
- package/scripts/validate-afyx-graph.py +203 -0
- package/scripts/validate-components.py +194 -0
- package/scripts/validate-engineering-assurance.py +281 -0
- package/scripts/verify-graph-archive.mjs +64 -0
- package/skills/afyx-context/SKILL.md +26 -0
- package/skills/afyx-engineering-expert/README.md +42 -0
- package/skills/afyx-engineering-expert/SKILL.md +70 -0
- package/skills/afyx-engineering-expert/assets/result-template.md +15 -0
- package/skills/afyx-engineering-expert/references/ai-ml-engineer.md +17 -0
- package/skills/afyx-engineering-expert/references/business-analyst.md +17 -0
- package/skills/afyx-engineering-expert/references/clean-code-engineer.md +26 -0
- package/skills/afyx-engineering-expert/references/code-reviewer.md +24 -0
- package/skills/afyx-engineering-expert/references/cybersecurity-devsecops.md +17 -0
- package/skills/afyx-engineering-expert/references/data-analyst-bi.md +24 -0
- package/skills/afyx-engineering-expert/references/data-engineer.md +24 -0
- package/skills/afyx-engineering-expert/references/database-administrator.md +17 -0
- package/skills/afyx-engineering-expert/references/debugging-specialist.md +24 -0
- package/skills/afyx-engineering-expert/references/embedded-iot-engineer.md +24 -0
- package/skills/afyx-engineering-expert/references/erp-technical-specialist.md +17 -0
- package/skills/afyx-engineering-expert/references/hardware-diagnostics-auditor.md +24 -0
- package/skills/afyx-engineering-expert/references/hardware-electronics-engineer.md +24 -0
- package/skills/afyx-engineering-expert/references/integration-engineer.md +24 -0
- package/skills/afyx-engineering-expert/references/legacy-modernization-engineer.md +24 -0
- package/skills/afyx-engineering-expert/references/llmops-prompt-engineer.md +24 -0
- package/skills/afyx-engineering-expert/references/network-engineer.md +24 -0
- package/skills/afyx-engineering-expert/references/performance-benchmark-engineer.md +24 -0
- package/skills/afyx-engineering-expert/references/platform-engineer.md +24 -0
- package/skills/afyx-engineering-expert/references/product-manager.md +17 -0
- package/skills/afyx-engineering-expert/references/qa-engineer.md +17 -0
- package/skills/afyx-engineering-expert/references/site-reliability-engineer.md +17 -0
- package/skills/afyx-engineering-expert/references/software-engineer.md +17 -0
- package/skills/afyx-engineering-expert/references/solutions-architect.md +17 -0
- package/skills/afyx-engineering-expert/references/specialists-index.md +33 -0
- package/skills/afyx-engineering-expert/references/subject-matter-expert.md +17 -0
- package/skills/afyx-engineering-expert/references/system-analyst.md +17 -0
- package/skills/afyx-engineering-expert/references/technical-project-manager.md +24 -0
- package/skills/afyx-engineering-expert/references/technical-writer.md +24 -0
- package/skills/afyx-engineering-expert/references/ui-ux-designer.md +17 -0
- package/skills/afyx-engineering-expert/workflows/ai-data-erp.md +20 -0
- package/skills/afyx-engineering-expert/workflows/debugging.md +10 -0
- package/skills/afyx-engineering-expert/workflows/discovery-design.md +11 -0
- package/skills/afyx-engineering-expert/workflows/implementation.md +12 -0
- package/skills/afyx-engineering-expert/workflows/incident-reliability.md +12 -0
- package/skills/afyx-engineering-expert/workflows/review-audit.md +13 -0
- package/skills/afyx-forge/SKILL.md +43 -0
- package/skills/afyx-forge/references/adaptive-policy.md +19 -0
- package/skills/efficient-coding/SKILL.md +33 -0
- package/skills/efficient-coding/references/investigation.md +27 -0
- package/skills/efficient-coding/references/token-efficiency.md +25 -0
- package/skills/efficient-coding/references/tool-routing.md +13 -0
- package/skills/odoo-engineering/SKILL.md +33 -0
- package/skills/odoo-engineering/references/common.md +9 -0
- package/skills/odoo-engineering/references/odoo-10.md +32 -0
- package/skills/odoo-engineering/references/odoo-11.md +26 -0
- package/skills/odoo-engineering/references/odoo-12.md +31 -0
- package/skills/odoo-engineering/references/odoo-13.md +27 -0
- package/skills/odoo-engineering/references/odoo-14.md +31 -0
- package/skills/odoo-engineering/references/odoo-15.md +34 -0
- package/skills/odoo-engineering/references/odoo-16.md +37 -0
- package/skills/odoo-engineering/references/odoo-17.md +37 -0
- package/skills/odoo-engineering/references/odoo-18.md +48 -0
- package/skills/odoo-engineering/references/odoo-19.md +43 -0
- package/skills/odoo-engineering/references/odoo-20.md +39 -0
- package/skills/odoo-engineering/references/reference-schema.md +16 -0
- package/skills/odoo-engineering/references/version-detection.md +13 -0
- package/tools/codex-usage/CodexUsage.psm1 +496 -0
- package/tools/codex-usage/codex-usage-doctor.ps1 +150 -0
- package/tools/codex-usage/codex-usage-pricing.json +25 -0
- package/tools/codex-usage/codex-usage-stop.ps1 +167 -0
- package/tools/codex-usage/codex-usage-watch.ps1 +250 -0
- package/tools/codex-usage/vscode-user-task.json +31 -0
- package/tools/windows-setup/SetupBootstrapper.cs +258 -0
- package/uninstall.ps1 +189 -0
- package/uninstall.sh +167 -0
- package/update.ps1 +95 -0
- package/update.sh +67 -0
- package/verify.ps1 +411 -0
- package/verify.sh +265 -0
|
@@ -0,0 +1,10 @@
|
|
|
1
|
+
# Workflow: Diagnosis → Minimal Fix → Regression
|
|
2
|
+
|
|
3
|
+
1. Capture observed symptom and expected outcome, time/version/environment, logs and reproducible steps; sanitize sensitive material.
|
|
4
|
+
2. Identify changed surface, hypotheses, and evidence required to distinguish them. Inspect root causes, not merely the visible UI message.
|
|
5
|
+
3. Reproduce or triangulate using safe methods; if not reproducible, say so and rank hypotheses by available evidence.
|
|
6
|
+
4. Identify smallest coherent fix, expected side effects, and rollback if necessary. Do not couple a broad refactor to an urgent fix.
|
|
7
|
+
5. Run a focused regression test and check relevant callers/permissions/data/concurrency.
|
|
8
|
+
6. Report root cause status (`confirmed` vs `probable`), implementation or recommendation, evidence, validation, and outstanding uncertainty.
|
|
9
|
+
|
|
10
|
+
If a live incident threatens availability or data integrity, use `incident-reliability.md` for containment-first decisions.
|
|
@@ -0,0 +1,11 @@
|
|
|
1
|
+
# Workflow: Discovery → Requirements → Design
|
|
2
|
+
|
|
3
|
+
Use for product discovery, a new feature, cross-team scope, system specification, or architecture decision. Skip irrelevant steps for smaller requests.
|
|
4
|
+
|
|
5
|
+
1. **Frame the outcome.** Confirm actor, problem, outcome, current evidence, constraints, and success criteria. Classify unverified statements as assumptions.
|
|
6
|
+
2. **Map requirements.** Identify roles and AS-IS/TO-BE processes, exceptional paths, business rules, privacy/security needs, and acceptance criteria. Resolve material contradictions with the requester or a documented assumption.
|
|
7
|
+
3. **Design appropriate level.** Choose a small viable set of options, compare tradeoffs, data and integration flow, permission boundaries, reliability, UX states, and measurable NFRs. Avoid gratuitous redesign.
|
|
8
|
+
4. **Decide and sequence.** Record choice, alternatives, scope/non-scope, dependencies, migration/rollout and reversibility. Define test and evidence required for acceptance.
|
|
9
|
+
5. **Deliver.** Provide decision-ready design proportionate to complexity, not an invented sign-off. For implementation handoff, include explicit acceptance criteria and unresolved questions.
|
|
10
|
+
|
|
11
|
+
Primary domains frequently include PM, BA, System Analyst, Architecture, UX, SME; select only those relevant to the work.
|
|
@@ -0,0 +1,12 @@
|
|
|
1
|
+
# Workflow: Bounded Implementation and Validation
|
|
2
|
+
|
|
3
|
+
Use only when implementation or file changes are requested and permitted.
|
|
4
|
+
|
|
5
|
+
1. **Preflight:** inspect repository instructions, relevant files, actual versions, current behavior, tests, worktree status, and requested scope. Avoid overwriting unrelated local work.
|
|
6
|
+
2. **Plan:** state the desired behavior, primary domain, other impacted components, security/data risks, minimal change, and matching validation. For high-risk changes, note rollback and authorization boundary.
|
|
7
|
+
3. **Implement:** change the smallest coherent surface, following existing conventions. Preserve backward compatibility unless explicitly changed. For schema/data/security changes, validate impacts across callers/roles/versions.
|
|
8
|
+
4. **Validate:** run the available targeted checks; cover intended result and negative/regression scenarios based on risk. Report exact commands and actual output status. Never assert screenshots or manual behavior without observation.
|
|
9
|
+
5. **Review:** inspect diff, check for stray files or secrets, note migration/config/documentation impact and remaining gaps. Do not silently deploy, push, publish, or alter production.
|
|
10
|
+
6. **Close:** short summary of changes, locations, validation PASS/FAIL/NOT RUN, limitations, and reviewer-ready test instructions where useful.
|
|
11
|
+
|
|
12
|
+
Recommended division of labor: Software Engineer primary; BA/System Analyst for acceptance; QA for evidence; Security/DBA/SRE/ERP/AI/UX if truly impacted.
|
|
@@ -0,0 +1,12 @@
|
|
|
1
|
+
# Workflow: Incident & Reliability
|
|
2
|
+
|
|
3
|
+
Use only for operational instability, outage, data risk, recovery or resilience design.
|
|
4
|
+
|
|
5
|
+
1. State observed impact, affected critical paths, onset, source/time of evidence, and uncertain facts. Classify severity provisionally using actual impact.
|
|
6
|
+
2. Prioritize user/data safety and containment: choose reversible mitigations, identify owner and permission for operational commands, protect evidence, and communicate status.
|
|
7
|
+
3. Assess rollback/failover/runbook options and their preconditions. Do not execute production-impacting changes without authorization.
|
|
8
|
+
4. Confirm recovery with user-facing signals and data integrity checks, not only process status. Monitor for recurrence.
|
|
9
|
+
5. Build a non-blaming timeline, contributing causes, missing detection/guardrails, and targeted follow-up actions.
|
|
10
|
+
6. If proactive SRE design: define representative SLIs/SLOs, alert thresholds, observability, capacity tests, and rollback from available baselines rather than fabricated targets.
|
|
11
|
+
|
|
12
|
+
Never promise to monitor later or perform continuous checks unless an available scheduling mechanism is configured and actually used.
|
|
@@ -0,0 +1,13 @@
|
|
|
1
|
+
# Workflow: Risk-Based Review / Audit
|
|
2
|
+
|
|
3
|
+
1. Define scope and review objective: PR/code, architecture, security, data, accessibility, AI, ERP process, or production readiness.
|
|
4
|
+
2. Gather actual artifacts, versions, diff, relevant requirements, tests, constraints and threat/context boundaries. Avoid assumptions about unseen files.
|
|
5
|
+
3. For automated read-only security audits, execute the native auditor:
|
|
6
|
+
`node scripts/afyx-security-auditor.mjs <targetDirectory>`
|
|
7
|
+
This scans for unsafe subprocesses, hardcoded secrets, injection, and path traversal with deterministic line-level evidence.
|
|
8
|
+
4. Inspect highest-impact failure modes first: correctness, broken user flow, data loss, authorization, secrets, compatibility, reliability and regression; then maintainability/style.
|
|
9
|
+
5. Record each finding with location/evidence, triggering condition, real-world impact, likelihood/confidence, concrete fix and optional validation. Distinguish confirmed defects from suggestions.
|
|
10
|
+
6. Prioritize by severity and relevance. If no issues are found, say what was reviewed and what remains untested; do not certify absolute safety.
|
|
11
|
+
7. Finish with concise findings ordered by risk, residual questions, and recommended verification.
|
|
12
|
+
|
|
13
|
+
Do not edit merely because a review was requested.
|
|
@@ -0,0 +1,43 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: afyx-forge
|
|
3
|
+
description: Standalone Afyx Forge Core adaptive engineering policy and actionable guidance engine. Formulates structured investigation plans, tool recommendations, validation scopes, and completion criteria for ordinary engineering tasks.
|
|
4
|
+
metadata:
|
|
5
|
+
version: "0.1.0"
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
# Afyx Forge Core — Adaptive Engineering Guidance
|
|
9
|
+
|
|
10
|
+
Afyx Forge Core turns engineering directives into bounded, structured, and actionable guidance without uncontrolled model costs or unauthorized autonomous operations.
|
|
11
|
+
|
|
12
|
+
## When to Use
|
|
13
|
+
|
|
14
|
+
Use `afyx-forge` when:
|
|
15
|
+
1. Approaching complex, cross-module, security-sensitive, or data-critical engineering tasks.
|
|
16
|
+
2. Formulating an adaptive execution plan before modifying unfamiliar codebases.
|
|
17
|
+
3. Deciding the proportional level of tooling (direct source vs. Afyx Graph vs. domain specialist) under the Afyx Adaptive Tool Routing discipline.
|
|
18
|
+
|
|
19
|
+
Do NOT use for trivial single-line changes, pure conversation, or when direct source inspection is already sufficient.
|
|
20
|
+
|
|
21
|
+
## CLI Usage
|
|
22
|
+
|
|
23
|
+
The standalone runtime is available via the CLI:
|
|
24
|
+
|
|
25
|
+
```bash
|
|
26
|
+
# Verify health, host surfaces, and component status
|
|
27
|
+
afyx-forge doctor
|
|
28
|
+
|
|
29
|
+
# Formulate plan from task description
|
|
30
|
+
afyx-forge plan --task "Refactor authentication tokens across api and storage services"
|
|
31
|
+
|
|
32
|
+
# Formulate plan from task file with markdown output
|
|
33
|
+
afyx-forge plan --task-file ./task.md --format markdown --output ./plan.md
|
|
34
|
+
```
|
|
35
|
+
|
|
36
|
+
## Core Principles
|
|
37
|
+
|
|
38
|
+
1. **Proportional Execution:** Select between `DIRECT_MINIMAL`, `FOCUSED_INVESTIGATION`, `STRUCTURAL_GRAPH_AWARE`, `DOMAIN_SPECIALIST`, and `SECURITY_DEFENSE_IN_DEPTH`.
|
|
39
|
+
2. **Graph-Aware Routing:** Use Afyx Graph only when cross-file relationships, inheritance, or impact analysis materially justify it. Fall back gracefully to direct-source tools when Graph is absent.
|
|
40
|
+
3. **Context Engine Default Enabled:** A healthy installed Context Engine is available without an opt-in variable; use it only for substantial or repeated context, honor explicit `AFYX_CONTEXT_OPT_IN=0`, and never claim Graph MCP interception without runtime evidence.
|
|
41
|
+
4. **Bounded Execution:** Forge operates in assistive guidance mode. Autonomous destructive operations, unapproved git push/commit, and secret leaks are strictly refused.
|
|
42
|
+
5. **Governance Integrity:** The formal A8 benchmark campaign remains `EVALUATION_GATED`. Forge Core Alpha provides guidance for day-to-day engineering without executing unapproved benchmark models.
|
|
43
|
+
|
|
@@ -0,0 +1,19 @@
|
|
|
1
|
+
# Afyx Forge Adaptive Policy Reference
|
|
2
|
+
|
|
3
|
+
## Execution Modes
|
|
4
|
+
|
|
5
|
+
| Execution Mode | Applicable Scenarios | Tooling Discipline |
|
|
6
|
+
| :--- | :--- | :--- |
|
|
7
|
+
| **`DIRECT_MINIMAL`** | Known file bugs, simple edits, typos, doc updates | Read target file directly, edit cleanly, run single unit test. Avoid Graph and Context. |
|
|
8
|
+
| **`FOCUSED_INVESTIGATION`** | Unknown defect diagnosis, flaky tests, stack traces | Reproduce failure signal first, isolate root-cause with ripgrep, verify fix. |
|
|
9
|
+
| **`STRUCTURAL_GRAPH_AWARE`** | Cross-module changes, inter-service API changes | Explore dependency graph via Afyx Graph (callers, callees, affected tests) or trace imports via ripgrep if Graph is absent. |
|
|
10
|
+
| **`DOMAIN_SPECIALIST`** | Framework-specific logic (e.g. Odoo ORM, XML views) | Engage domain engineering guidelines (e.g. Odoo Engineering Skill). Track inheritance and schema versions. |
|
|
11
|
+
| **`SECURITY_DEFENSE_IN_DEPTH`** | Auth, tokens, crypto, permissions, ACL, data sanitization | Perform security boundary audit, fail closed, write negative regression tests. |
|
|
12
|
+
|
|
13
|
+
## Bounded Execution Rules
|
|
14
|
+
|
|
15
|
+
Forge Core enforces strict safety boundaries:
|
|
16
|
+
1. **No Autonomous Commits/Pushes:** Requests containing force-push, bypassing review gates, or automatic branch publishing without explicit owner authorization are refused with status `REFUSED_UNSAFE`.
|
|
17
|
+
2. **No Secret Exfiltration:** Directives that attempt to dump, expose, or transmit credentials or private keys are immediately blocked.
|
|
18
|
+
3. **No Destructive Drops:** Refuse commands requesting table drops, mass file deletions, or disk formatting without prior backup and authorization.
|
|
19
|
+
|
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: efficient-coding
|
|
3
|
+
description: Quality-first workflow for software implementation, debugging, refactoring, and code investigation. Applies to coding work, not general conversation, prompt writing, or document-only tasks.
|
|
4
|
+
metadata:
|
|
5
|
+
version: "1.2.2"
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
# Efficient Coding
|
|
9
|
+
|
|
10
|
+
Prioritize **correctness → evidence → scoped change → validation → efficiency**. The target repository is authoritative.
|
|
11
|
+
|
|
12
|
+
## Core loop
|
|
13
|
+
|
|
14
|
+
- **GROUND:** establish the requested target, observable problem or outcome, material impact, and validation signal.
|
|
15
|
+
- **LOCATE:** route known targets directly, narrow unknown defects from evidence, and trace cross-cutting relationships only as far as correctness requires.
|
|
16
|
+
- **REPRODUCE:** for bugs, establish a reliable failure signal or behavioral baseline before changing code when feasible.
|
|
17
|
+
- **CHANGE:** make the smallest safe, authorized change that resolves the evidenced problem.
|
|
18
|
+
- **VALIDATE:** run focused checks first, expanding only for material regression risk.
|
|
19
|
+
- **REPORT:** be concise by default; include the evidence and detail warranted by task complexity.
|
|
20
|
+
|
|
21
|
+
Read `references/investigation.md` when the target, reproduction, impact, or change boundary is unclear. Read `references/tool-routing.md` when tool choice matters. For genuinely large or noisy evidence, read `references/token-efficiency.md`.
|
|
22
|
+
|
|
23
|
+
## Change contract
|
|
24
|
+
|
|
25
|
+
For materially ambiguous work, surface the assumption and tradeoff that affects correctness. Prefer a simpler supported approach; ask only when missing information blocks a safe decision.
|
|
26
|
+
|
|
27
|
+
Do not introduce speculative abstractions, flags, dependencies, or adjacent cleanups. Match existing conventions and remove only the newly unused code caused by your changes.
|
|
28
|
+
|
|
29
|
+
For multistep changes, define a short sequence with observable acceptance checks. A task is not complete merely because code was written; distinguish executed PASS from untested or blocked validation.
|
|
30
|
+
|
|
31
|
+
Preserve relevant architecture, compatibility, conventions, and public behavior. Existing explicit user authorization is sufficient within its stated scope; request approval before unapproved destructive operations, dependencies, public API/schema changes, or scope expansion.
|
|
32
|
+
|
|
33
|
+
Stop exploring once material uncertainty is resolved. Never trade away evidence required for a correct result merely to reduce tool calls or tokens.
|
|
@@ -0,0 +1,27 @@
|
|
|
1
|
+
# Investigation routing
|
|
2
|
+
|
|
3
|
+
## Ground the task
|
|
4
|
+
|
|
5
|
+
Before editing, identify the requested target, observable problem or expected outcome, material impact, and the validation signal that will distinguish success from an unverified change. Repository evidence overrides assumptions.
|
|
6
|
+
|
|
7
|
+
## Known target
|
|
8
|
+
|
|
9
|
+
Start at the named method, field, file, stack frame, or failing test. Inspect callers, dependencies, inheritance, configuration, and tests only when they can change the safe implementation or validation boundary. Do not begin with a repository-wide scan.
|
|
10
|
+
|
|
11
|
+
## Unknown target
|
|
12
|
+
|
|
13
|
+
Anchor on the observable signal: error text, missing UI element, request route, log window, or reproduction. Establish a reliable failure signal or behavioral baseline when feasible. Search for candidates, compare and narrow them, then read the authoritative implementation and trace only relevant relationships. Avoid opening every candidate in full.
|
|
14
|
+
|
|
15
|
+
## Cross-cutting or architectural
|
|
16
|
+
|
|
17
|
+
Find the source of truth before editing. Trace consumers, callers, inheritance, dependency paths, configuration, and persistence boundaries. State the impact boundary, preserve existing contracts, and validate representative downstream paths.
|
|
18
|
+
|
|
19
|
+
## Change and cost boundary
|
|
20
|
+
|
|
21
|
+
Make the smallest safe change supported by the evidence. Existing explicit user authorization is sufficient within its stated scope. Request approval before unapproved destructive operations, new dependencies, public API or schema changes, or material scope expansion.
|
|
22
|
+
|
|
23
|
+
When relevant, check algorithmic complexity, N+1 behavior, memory, I/O, and concurrency. Treat these as risk lenses, not mandatory ceremony for simple changes.
|
|
24
|
+
|
|
25
|
+
## Stopping rule
|
|
26
|
+
|
|
27
|
+
Stop gathering context when the source, behavior, impact, and validation boundary are sufficiently evidenced. More exploration is not safer when it only repeats established facts.
|
|
@@ -0,0 +1,25 @@
|
|
|
1
|
+
# Large-context guidance
|
|
2
|
+
|
|
3
|
+
Use this reference only when repository exploration or tool output is large enough to create avoidable context overhead.
|
|
4
|
+
|
|
5
|
+
## Exploration strategy
|
|
6
|
+
|
|
7
|
+
For a known target, begin with that definition or failing path, then inspect only the relationships and behavior needed to establish impact. For an unknown target, search to identify candidates, compare the relevant ones, then narrow before reading implementations in depth. A repository-wide search is appropriate only when the question itself is repository-wide.
|
|
8
|
+
|
|
9
|
+
Do not repeat an unchanged search, reread unchanged material, or request a full file when the relevant symbol or section is sufficient. Preserve a compact record of established facts rather than recreating the same investigation.
|
|
10
|
+
|
|
11
|
+
## Tool boundaries
|
|
12
|
+
|
|
13
|
+
Use Afyx Graph when resolving relationships is the efficient way to answer a structural question. Prefer direct search or focused reads for known locations and simple textual facts.
|
|
14
|
+
|
|
15
|
+
For genuinely large logs, test output, search results, JSON, API responses,
|
|
16
|
+
database output, or generated tool output, filter or summarize at the source when
|
|
17
|
+
that preserves the needed meaning. Do not compress small results by default.
|
|
18
|
+
Retrieve the original output before relying on an exact line, value, order, or
|
|
19
|
+
detail that a summary could omit.
|
|
20
|
+
|
|
21
|
+
## Validation and reporting
|
|
22
|
+
|
|
23
|
+
Start with the narrowest check that can disprove the change, then expand according to shared behavior and material regression risk. Do not repeat unchanged checks.
|
|
24
|
+
|
|
25
|
+
Report concisely by default: outcome or root cause, changed scope, validation, and remaining uncertainty. Increase detail when task complexity, risk, or evidence requires it; do not force a fixed report length. Record token, time, or tool savings only when actually measured.
|
|
@@ -0,0 +1,13 @@
|
|
|
1
|
+
# Tool routing — Afyx-first, permitted external fallback
|
|
2
|
+
|
|
3
|
+
Use direct source reads or targeted text search for known symbols, simple textual facts, configuration and localized changes. Do not call a graph merely to inspect a known file or small function.
|
|
4
|
+
|
|
5
|
+
**Afyx-first** is a per-capability, per-surface preference: when relationship, cross-module impact, or affected-test analysis materially helps, prefer an installed, enabled, authorized, reachable, healthy, compatible and fresh Afyx-family tool (such as `afyx_graph_*` MCP or `afyx-graph` CLI). A legacy external index directory, CLI binary on PATH, or older routing instruction must not displace a usable Afyx equivalent.
|
|
6
|
+
|
|
7
|
+
When the Afyx equivalent is **not installed**, unsupported, unavailable or unsuitable, an independently installed **external fallback** MAY be used if its exact MCP/CLI surface is explicitly enabled and authorized, and the owner permits external fallback. Disabling an external MCP does NOT silently authorize its CLI, aliases, wrappers or subprocess. Do not auto-install external tools, copy external code into Afyx, change user configuration, bypass denied permissions or silently re-enable a deliberately disabled Afyx component.
|
|
8
|
+
|
|
9
|
+
When the Afyx index is stale, partial or unindexed, return to authoritative direct source inspection; an owner-permitted external equivalent may be considered only when it materially improves the required capability. If no authorized suitable tool exists, use direct source-backed reading/search and disclose unsupported coverage.
|
|
10
|
+
|
|
11
|
+
Apply the same Afyx-first policy to **all other Afyx tool families**, including future components. Select by required capability, verified installed/enabled/health status and user-controlled surface permissions, not branding or apparent CLI availability. Provider compatibility and feature parity must be verified. See `docs/AFYX_TOOL_FAMILY_ROUTING.md` for the v1 routing decision contract.
|
|
12
|
+
|
|
13
|
+
For noisy results, narrow at the source and preserve exact original evidence for values, lines, ordering and stack traces. Stop after the material question is answered; use the smallest sufficient evidence path.
|
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: odoo-engineering
|
|
3
|
+
description: Version-aware Odoo engineering for Odoo repositories, modules, ORM, views, reports, security, migrations, and debugging. Stable references cover Odoo 10–20; select one target version from repository evidence.
|
|
4
|
+
metadata:
|
|
5
|
+
version: "1.2.0"
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
# Odoo Engineering
|
|
9
|
+
|
|
10
|
+
Apply only to Odoo work. Determine the actual major version from repository/runtime evidence before using version-specific behavior. Prefer `odoo/release.py`, release metadata, `odoo-bin --version`, explicit branch/tag, server runtime, manifest conventions, dependency files, and established code patterns.
|
|
11
|
+
|
|
12
|
+
For a simple explanation without a target repository or runtime, avoid heavyweight investigation: state the assumed Odoo version or ask for it only when the answer materially depends on the release.
|
|
13
|
+
|
|
14
|
+
Never import Python/runtime features, ORM APIs, view/XML syntax, JavaScript/OWL modules, asset declarations, security behavior, report patterns, or migration conventions from another release based on familiarity. Repository evidence is authoritative.
|
|
15
|
+
|
|
16
|
+
## Routing
|
|
17
|
+
|
|
18
|
+
1. Read `references/common.md` for all Odoo tasks.
|
|
19
|
+
2. Determine one target version from repository/runtime evidence. Read `references/version-detection.md` when evidence is missing or conflicting.
|
|
20
|
+
3. Read exactly one `references/odoo-<version>.md` for a normal task. For a migration, read only the source and target references that are actually required.
|
|
21
|
+
4. Inspect the actual module inheritance, manifest dependencies, model/view references, and local patterns needed for the task.
|
|
22
|
+
|
|
23
|
+
If evidence conflicts, do not guess: report the conflict, prioritize executable/source/runtime evidence, and use only the version it proves. Never mix APIs from conflicting versions. For upgrades, treat source and target versions separately.
|
|
24
|
+
|
|
25
|
+
`references/reference-schema.md` defines the compact evidence-backed shape for future version-reference expansion; it is not a reason to load every version reference for one task.
|
|
26
|
+
|
|
27
|
+
For an Odoo upgrade spanning versions, treat each source and target version separately. Do not convert an existing module merely because a newer pattern exists.
|
|
28
|
+
|
|
29
|
+
## Scope and validation
|
|
30
|
+
|
|
31
|
+
Search before editing. For model behavior inspect inheritance, fields, compute/onchange/constraint methods, access rules, domains, and callers when material. For views inspect external IDs, parent views, inheritance chains, xpath targets, and module dependencies.
|
|
32
|
+
|
|
33
|
+
Prefer a targeted module update or test first. Do not run a full database update, alter production data, change schema, or perform a migration without explicit authorization.
|
|
@@ -0,0 +1,9 @@
|
|
|
1
|
+
# Common Odoo evidence rules
|
|
2
|
+
|
|
3
|
+
The repository is the source of truth. Before changing code, establish the Odoo release, Python runtime, module dependencies, and applicable custom inheritance. Odoo tasks may cross Python/backend, XML views, QWeb, JavaScript/OWL, assets, controllers, or reports; inspect only the relevant boundary.
|
|
4
|
+
|
|
5
|
+
For models, inspect `_name`, `_inherit`, `_inherits`, override/`super` chains, fields, computed dependencies, inverse/search methods, `@api.depends`, onchange/constraints, create/write/unlink overrides, recordset and multi-record behavior, access rights, record rules, domains, company boundaries, `sudo`, and affected callers as relevant. Check batching, prefetch behavior, and N+1 query risk when the changed path can process multiple records. For XML, resolve the external ID, model, parent view, inheritance order, xpath target, priority, and module dependency before editing.
|
|
6
|
+
|
|
7
|
+
Treat ACLs, record rules, field groups and group implications, view visibility, business validation, company boundaries, and `sudo` as different controls. UI visibility is not security. `sudo` is an explicit privilege boundary because it bypasses normal access-right and record-rule checks; keep its scope minimal and do not use it to mask authorization defects. Preserve persisted technical identifiers, database columns, XML IDs, context keys, and stored values unless an authorized migration explicitly requires changing them; a display-label change alone is not authorization.
|
|
8
|
+
|
|
9
|
+
Validate the affected module first. Expand testing only when shared models, inherited views, security, reporting, frontend/backend boundaries, integrations, or dependencies raise regression risk.
|
|
@@ -0,0 +1,32 @@
|
|
|
1
|
+
# Odoo 10
|
|
2
|
+
|
|
3
|
+
Status: stable
|
|
4
|
+
Last verified: 2026-09-23
|
|
5
|
+
|
|
6
|
+
## Runtime baseline
|
|
7
|
+
|
|
8
|
+
- Exact `10.0/odoo/release.py` identifies Odoo 10. Exact `10.0/setup.py` does not declare `python_requires`; inspect the target deployment/runtime before changing Python syntax.
|
|
9
|
+
- Exact `10.0/addons/web/__manifest__.py` does not use the later manifest `assets` key. Do not copy that later asset declaration shape into an Odoo 10 module without repository evidence.
|
|
10
|
+
|
|
11
|
+
## High-risk version traps
|
|
12
|
+
|
|
13
|
+
- Treat Odoo 10 as a legacy boundary. Do not backport OWL, modern JavaScript imports, newer asset-bundle declarations, or newer view/ORM conveniences based on familiarity.
|
|
14
|
+
- Preserve the target repository's existing ORM, XML, QWeb, and web-module patterns; validate migrations/backports against the actual 10.0 source and deployment runtime.
|
|
15
|
+
|
|
16
|
+
## Validation
|
|
17
|
+
|
|
18
|
+
Prefer targeted Python/module import, XML loading, and affected report/web asset checks in the target Odoo 10 environment.
|
|
19
|
+
|
|
20
|
+
## Evidence
|
|
21
|
+
|
|
22
|
+
- Official source: `https://github.com/odoo/odoo/blob/10.0/odoo/release.py`
|
|
23
|
+
- Official source: `https://github.com/odoo/odoo/blob/10.0/setup.py`
|
|
24
|
+
- Official source: `https://github.com/odoo/odoo/blob/10.0/addons/web/__manifest__.py`
|
|
25
|
+
|
|
26
|
+
## ORM / Python
|
|
27
|
+
|
|
28
|
+
Exact `10.0/odoo/api.py` defines `multi()` and `one()`. Odoo 10 code can therefore contain legacy/new-API coexistence; do not mechanically replace working decorators or imports during maintenance.
|
|
29
|
+
|
|
30
|
+
## Frontend / JavaScript
|
|
31
|
+
|
|
32
|
+
Treat the legacy web module and import generation as a compatibility boundary. Do not introduce OWL or modern module/asset patterns without target-repository evidence.
|
|
@@ -0,0 +1,26 @@
|
|
|
1
|
+
# Odoo 11
|
|
2
|
+
|
|
3
|
+
Status: stable
|
|
4
|
+
Last verified: 2026-09-23
|
|
5
|
+
|
|
6
|
+
## Runtime baseline
|
|
7
|
+
|
|
8
|
+
- Official `11.0/setup.py` declares `python_requires >=3.5`; confirm deployed runtime and repository constraints.
|
|
9
|
+
- Official `11.0/addons/web/__manifest__.py` does not use the later manifest `assets` key.
|
|
10
|
+
|
|
11
|
+
## High-risk version traps
|
|
12
|
+
|
|
13
|
+
Keep Odoo 11 ORM, view, QWeb, and web-module conventions local to the target repository. Do not infer compatibility from Odoo 12+ examples.
|
|
14
|
+
|
|
15
|
+
## Validation
|
|
16
|
+
|
|
17
|
+
Use targeted module import/update, XML loading, and affected web/report checks under the target Odoo 11 runtime.
|
|
18
|
+
|
|
19
|
+
## Evidence
|
|
20
|
+
|
|
21
|
+
- Official source: `https://github.com/odoo/odoo/blob/11.0/setup.py`
|
|
22
|
+
- Official source: `https://github.com/odoo/odoo/blob/11.0/addons/web/__manifest__.py`
|
|
23
|
+
|
|
24
|
+
## ORM / Python
|
|
25
|
+
|
|
26
|
+
Exact `11.0/odoo/api.py` still defines `multi()` and `one()`. Preserve recordset/decorator semantics during maintenance and inspect the 12→13 boundary before migration.
|
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
# Odoo 12
|
|
2
|
+
|
|
3
|
+
Status: stable
|
|
4
|
+
Last verified: 2026-09-23
|
|
5
|
+
|
|
6
|
+
## Runtime baseline
|
|
7
|
+
|
|
8
|
+
- Official `12.0/setup.py` declares `python_requires >=3.5`; inspect target deployment/runtime rather than assuming a newer baseline.
|
|
9
|
+
- Official `12.0/addons/web/__manifest__.py` does not use the later manifest `assets` key.
|
|
10
|
+
|
|
11
|
+
## High-risk version traps
|
|
12
|
+
|
|
13
|
+
Keep Odoo 12 model, view, report, and web asset conventions tied to repository evidence. Do not import Odoo 13+ changes without checking exact source behavior.
|
|
14
|
+
|
|
15
|
+
## Validation
|
|
16
|
+
|
|
17
|
+
Validate the affected module, XML inheritance, report path, and web assets with the target Odoo 12 runtime.
|
|
18
|
+
|
|
19
|
+
## ORM / Python
|
|
20
|
+
|
|
21
|
+
Exact `12.0/odoo/api.py` defines `multi()`, `one()`, and `model_create_multi()`. Do not collapse Odoo 12 recordset behavior into post-13 assumptions; inspect method semantics and callers when migrating.
|
|
22
|
+
|
|
23
|
+
## Migration trap: 12 → 13
|
|
24
|
+
|
|
25
|
+
The decorator boundary must be handled semantically, not by a mechanical `ensure_one()` rewrite.
|
|
26
|
+
|
|
27
|
+
## Evidence
|
|
28
|
+
|
|
29
|
+
- Official source: `https://github.com/odoo/odoo/blob/12.0/setup.py`
|
|
30
|
+
- Official source: `https://github.com/odoo/odoo/blob/12.0/addons/web/__manifest__.py`
|
|
31
|
+
- Official source: `https://github.com/odoo/odoo/blob/12.0/odoo/api.py`
|
|
@@ -0,0 +1,27 @@
|
|
|
1
|
+
# Odoo 13
|
|
2
|
+
|
|
3
|
+
Status: stable
|
|
4
|
+
Last verified: 2026-09-23
|
|
5
|
+
|
|
6
|
+
## Runtime baseline
|
|
7
|
+
|
|
8
|
+
- Official `13.0/setup.py` declares `python_requires >=3.6`; inspect the actual deployment/runtime as well.
|
|
9
|
+
- Official `13.0/addons/web/__manifest__.py` does not use the later manifest `assets` key.
|
|
10
|
+
|
|
11
|
+
## High-risk version traps
|
|
12
|
+
|
|
13
|
+
Verify Odoo 13 manifest, ORM, view, report, and JavaScript conventions against exact source before importing newer examples.
|
|
14
|
+
|
|
15
|
+
## Validation
|
|
16
|
+
|
|
17
|
+
Prefer targeted Python/module, XML, report, and affected web checks under the target Odoo 13 runtime.
|
|
18
|
+
|
|
19
|
+
## ORM / Python
|
|
20
|
+
|
|
21
|
+
Exact `13.0/odoo/api.py` defines `model_create_multi()` but no longer defines `multi()` or `one()`. Do not generate those Odoo 12-era decorators for Odoo 13+; preserve recordset semantics rather than assuming every method is singleton.
|
|
22
|
+
|
|
23
|
+
## Evidence
|
|
24
|
+
|
|
25
|
+
- Official source: `https://github.com/odoo/odoo/blob/13.0/setup.py`
|
|
26
|
+
- Official source: `https://github.com/odoo/odoo/blob/13.0/addons/web/__manifest__.py`
|
|
27
|
+
- Official source: `https://github.com/odoo/odoo/blob/13.0/odoo/api.py`
|
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
# Odoo 14
|
|
2
|
+
|
|
3
|
+
Status: stable
|
|
4
|
+
Last verified: 2026-09-23
|
|
5
|
+
|
|
6
|
+
## Runtime baseline
|
|
7
|
+
|
|
8
|
+
- Official `14.0/setup.py` declares `python_requires >=3.6`.
|
|
9
|
+
- Official `14.0/addons/web/__manifest__.py` does not use the later manifest `assets` key.
|
|
10
|
+
|
|
11
|
+
## High-risk version traps
|
|
12
|
+
|
|
13
|
+
Treat Odoo 14 as its own compatibility boundary. Inspect exact framework, ORM, view, and asset conventions before importing a newer pattern.
|
|
14
|
+
|
|
15
|
+
## Validation
|
|
16
|
+
|
|
17
|
+
Validate the affected module, inherited XML, and relevant frontend/report loading under the target Odoo 14 runtime.
|
|
18
|
+
|
|
19
|
+
## ORM / Python
|
|
20
|
+
|
|
21
|
+
An exact source search of `14.0/odoo/fields.py` found no `class Command`. Do not generate `fields.Command.create/update/set` for Odoo 14 unless the target repository provides its own compatibility abstraction; inspect the existing tuple-command pattern and RPC boundary.
|
|
22
|
+
|
|
23
|
+
## Migration trap: 14 → 15
|
|
24
|
+
|
|
25
|
+
The absence claim is source-based, not documentation-silence-based. Verify custom abstractions before changing working relational commands.
|
|
26
|
+
|
|
27
|
+
## Evidence
|
|
28
|
+
|
|
29
|
+
- Official source: `https://github.com/odoo/odoo/blob/14.0/setup.py`
|
|
30
|
+
- Official source: `https://github.com/odoo/odoo/blob/14.0/addons/web/__manifest__.py`
|
|
31
|
+
- Official source: `https://github.com/odoo/odoo/blob/14.0/odoo/fields.py`
|
|
@@ -0,0 +1,34 @@
|
|
|
1
|
+
# Odoo 15
|
|
2
|
+
|
|
3
|
+
Status: stable
|
|
4
|
+
Last verified: 2026-09-23
|
|
5
|
+
|
|
6
|
+
## Runtime baseline and assets
|
|
7
|
+
|
|
8
|
+
- Official `15.0/setup.py` declares `python_requires >=3.7`.
|
|
9
|
+
- Exact `15.0/addons/web/__manifest__.py` is the first inspected branch in this set that declares the manifest `assets` key. Do not backport this loading shape to 14.0 or earlier without evidence.
|
|
10
|
+
|
|
11
|
+
## High-risk version traps
|
|
12
|
+
|
|
13
|
+
Confirm Odoo 15 backend/frontend conventions before changing established module APIs. Asset loading is a version boundary; inspect the exact manifest and bundle names.
|
|
14
|
+
|
|
15
|
+
## Validation
|
|
16
|
+
|
|
17
|
+
Validate the affected module, XML, asset bundle, and integration surface under Odoo 15.
|
|
18
|
+
|
|
19
|
+
## ORM / Python
|
|
20
|
+
|
|
21
|
+
Exact `15.0/odoo/fields.py` defines `class Command` with helpers including `create`, `update`, `delete`, `unlink`, `link`, `clear`, and `set`. Use it only when the target version supports it.
|
|
22
|
+
|
|
23
|
+
Python helpers do not change the RPC representation automatically; inspect integrations that require literal three-element relational command tuples.
|
|
24
|
+
|
|
25
|
+
## Frontend / JavaScript
|
|
26
|
+
|
|
27
|
+
Odoo 15 official JavaScript documentation describes `@odoo-module` as the opt-in marker for native-module conversion while legacy `odoo.define` and external/plain JavaScript remain compatibility concerns. Inspect local module style before changing it.
|
|
28
|
+
|
|
29
|
+
## Evidence
|
|
30
|
+
|
|
31
|
+
- Official source: `https://github.com/odoo/odoo/blob/15.0/setup.py`
|
|
32
|
+
- Official source: `https://github.com/odoo/odoo/blob/15.0/addons/web/__manifest__.py`
|
|
33
|
+
- Official source: `https://github.com/odoo/odoo/blob/15.0/odoo/fields.py`
|
|
34
|
+
- Official documentation: `https://www.odoo.com/documentation/15.0/developer/reference/frontend/javascript_modules.html`
|
|
@@ -0,0 +1,37 @@
|
|
|
1
|
+
# Odoo 16
|
|
2
|
+
|
|
3
|
+
Status: stable
|
|
4
|
+
Last verified: 2026-09-23
|
|
5
|
+
|
|
6
|
+
## Runtime baseline and assets
|
|
7
|
+
|
|
8
|
+
- Official `16.0/setup.py` declares `python_requires >=3.7`.
|
|
9
|
+
- Exact `16.0/addons/web/__manifest__.py` declares the manifest `assets` key; inspect exact bundle declarations rather than copying a neighboring version.
|
|
10
|
+
|
|
11
|
+
## High-risk version traps
|
|
12
|
+
|
|
13
|
+
Use target-repository Odoo 16 patterns for ORM, views, assets, and client code. Treat frontend/backend crossings as separate validation surfaces.
|
|
14
|
+
|
|
15
|
+
## Validation
|
|
16
|
+
|
|
17
|
+
Validate the affected Python/module path, inherited views, and relevant asset/client bundle under Odoo 16.
|
|
18
|
+
|
|
19
|
+
## Evidence
|
|
20
|
+
|
|
21
|
+
- Official source: `https://github.com/odoo/odoo/blob/16.0/setup.py`
|
|
22
|
+
- Official source: `https://github.com/odoo/odoo/blob/16.0/addons/web/__manifest__.py`
|
|
23
|
+
- Official Odoo 16 ORM changelog — translated fields stored as JSONB; `search_count(limit)` behavior
|
|
24
|
+
- Official documentation: `https://www.odoo.com/documentation/16.0/developer/reference/backend/orm.html` — `attrs` / `states` dynamic-view era
|
|
25
|
+
|
|
26
|
+
## Delta from previous major
|
|
27
|
+
|
|
28
|
+
- Translated fields are stored as `JSONB` in Odoo 16; migration, reporting, and custom SQL must not assume pre-16 translation storage.
|
|
29
|
+
- `search_count()` takes `limit` into account. Recheck partial/existence-like counts and performance-sensitive code ported from older versions.
|
|
30
|
+
|
|
31
|
+
## ORM / Python
|
|
32
|
+
|
|
33
|
+
Use the exact Odoo 16 count and translation semantics above; method availability alone is not an introduction-version claim.
|
|
34
|
+
|
|
35
|
+
## Views / XML
|
|
36
|
+
|
|
37
|
+
Odoo 16 documentation remains the reference for the `attrs`/`states`-era dynamic-view patterns. When migrating to 17+, inspect the target architecture rather than mechanically carrying those attributes forward.
|
|
@@ -0,0 +1,37 @@
|
|
|
1
|
+
# Odoo 17
|
|
2
|
+
|
|
3
|
+
Status: stable
|
|
4
|
+
Last verified: 2026-09-23
|
|
5
|
+
|
|
6
|
+
## Runtime baseline and assets
|
|
7
|
+
|
|
8
|
+
- Official `17.0/setup.py` declares `python_requires >=3.10`.
|
|
9
|
+
- Exact `17.0/addons/web/__manifest__.py` declares the manifest `assets` key.
|
|
10
|
+
|
|
11
|
+
## High-risk version traps
|
|
12
|
+
|
|
13
|
+
Keep Odoo 17 server and client implementation checks separate when a task crosses the UI boundary. Validate inherited views and assets narrowly before changing frontend code; do not carry 18–20 assumptions backward.
|
|
14
|
+
|
|
15
|
+
## Validation
|
|
16
|
+
|
|
17
|
+
Use targeted Python/module, XML view, and asset/client checks under the target Odoo 17 runtime.
|
|
18
|
+
|
|
19
|
+
## Evidence
|
|
20
|
+
|
|
21
|
+
- Official source: `https://github.com/odoo/odoo/blob/17.0/setup.py`
|
|
22
|
+
- Official source: `https://github.com/odoo/odoo/blob/17.0/addons/web/__manifest__.py`
|
|
23
|
+
- Official source: `https://github.com/odoo/odoo/blob/17.0/odoo/tools/sql.py`
|
|
24
|
+
- Official documentation: `https://www.odoo.com/documentation/17.0/developer/reference/frontend/javascript_modules.html`
|
|
25
|
+
- Official documentation: `https://www.odoo.com/documentation/17.0/developer/reference/user_interface/view_architectures.html`
|
|
26
|
+
|
|
27
|
+
## ORM / Python
|
|
28
|
+
|
|
29
|
+
Exact `17.0/odoo/tools/sql.py` defines the `SQL` wrapper. Prefer ORM where appropriate; when custom SQL is required, inspect the target 17.0 wrapper/source instead of copying raw-SQL patterns blindly.
|
|
30
|
+
|
|
31
|
+
## Views / XML
|
|
32
|
+
|
|
33
|
+
Odoo 17 view documentation describes direct Python-expression modifiers such as `invisible`, `readonly`, and `required`. Do not copy Odoo 16 `attrs`/`states` patterns without checking the target repository; this wording does not by itself claim every legacy attribute is rejected.
|
|
34
|
+
|
|
35
|
+
## Frontend / JavaScript
|
|
36
|
+
|
|
37
|
+
Odoo 17 JavaScript documentation uses `@odoo-module` as the native-module conversion marker. Inspect local module style before adding or removing the marker.
|
|
@@ -0,0 +1,48 @@
|
|
|
1
|
+
# Odoo 18
|
|
2
|
+
|
|
3
|
+
Status: stable
|
|
4
|
+
Last verified: 2026-09-23
|
|
5
|
+
|
|
6
|
+
## Runtime baseline and assets
|
|
7
|
+
|
|
8
|
+
- Official `18.0/setup.py` declares `python_requires >=3.10`.
|
|
9
|
+
- Exact `18.0/addons/web/__manifest__.py` declares the manifest `assets` key.
|
|
10
|
+
|
|
11
|
+
## High-risk version traps
|
|
12
|
+
|
|
13
|
+
Select Odoo 18 APIs and conventions from the target repository and exact source. Do not apply generic latest-version guidance or assume Odoo 17/19 behavior is identical.
|
|
14
|
+
|
|
15
|
+
## Validation
|
|
16
|
+
|
|
17
|
+
Validate affected ORM, inherited XML, and relevant frontend/asset paths under Odoo 18.
|
|
18
|
+
|
|
19
|
+
## Evidence
|
|
20
|
+
|
|
21
|
+
- Official source: `https://github.com/odoo/odoo/blob/18.0/setup.py`
|
|
22
|
+
- Official source: `https://github.com/odoo/odoo/blob/18.0/addons/web/__manifest__.py`
|
|
23
|
+
- Official documentation: `https://www.odoo.com/documentation/18.0/developer/reference/backend/orm.html` — `_search_display_name`, access helpers, Environment translations
|
|
24
|
+
- Official documentation: `https://www.odoo.com/documentation/18.0/developer/reference/frontend/javascript_modules.html`
|
|
25
|
+
- Official documentation: `https://www.odoo.com/documentation/18.0/developer/reference/user_interface/view_architectures.html` — `<list>` root and `<tree>` previous name
|
|
26
|
+
- Official Odoo ORM changelog — `aggregator` rename in Online 17.2 (inherited by stable 18)
|
|
27
|
+
|
|
28
|
+
## Delta from previous major
|
|
29
|
+
|
|
30
|
+
- `_search_display_name` implements name searching like other fields. When adapting custom name-search behavior, inspect `_search_display_name` and display-name behavior before carrying older overrides forward.
|
|
31
|
+
- `check_access`, `has_access`, and `_filtered_access` combine access-right and rule handling. They are available helpers, not a mandate to mechanically replace existing `check_access_rights` plus `check_access_rule` calls.
|
|
32
|
+
- Translations are available from the `Environment`; keep translation changes scoped to the actual call site.
|
|
33
|
+
|
|
34
|
+
### Stable-line inherited terminology
|
|
35
|
+
|
|
36
|
+
Odoo 18 stable uses post-17.2 `aggregator` terminology (`group_operator` → `aggregator`); that rename originated in the Odoo Online 17.2 line, not in 18.0. JSONB translation storage is an Odoo 16 change and is inherited, not an Odoo 18 introduction.
|
|
37
|
+
|
|
38
|
+
## ORM / Python
|
|
39
|
+
|
|
40
|
+
Use the 18.0 helpers above only after checking call-site semantics; availability does not require refactoring.
|
|
41
|
+
|
|
42
|
+
## Views / XML
|
|
43
|
+
|
|
44
|
+
The official 18.0 view architecture names the root element of list views `list` and identifies `tree` as its previous name. Before changing XML, inspect view type identifiers, inheritance XPath targets, and external inherited views; do not assume `tree` is rejected solely from the documentation wording.
|
|
45
|
+
|
|
46
|
+
## Frontend / JavaScript
|
|
47
|
+
|
|
48
|
+
Odoo 18 documentation describes files under `/static/src` and `/static/tests` as automatically transpiled into Odoo modules. Do not blindly add or remove `@odoo-module`; inspect local source and aliases first.
|