Purpose
This is the focused discussion issue for RFC-0001: erp-agent.
The RFC was originally drafted as wasmagent-js#8 and has been migrated here since it spans multiple repos.
What needs a decision (Phase 1 scope)
RFC-0001 lists six open questions. The three that block Phase 1 are:
-
First ERP target — Odoo (recommended) or NetSuite? This determines which SDK, test environment, and verifier examples land in the PoC.
-
@wasmagent/worker-template — extract now or later? RFC recommendation is later (copy bscode first, extract after two repos prove the pattern). Any objections?
-
Repo visibility — public from day one (matches bscode) or private until the PoC is presentable?
Not in scope here
- AEP v0.3 design questions → wasmagent-js#7
- Verifier package ownership (
@wasmagent/erp-verifiers vs in-repo) — can wait until Phase 2
How to engage
Comment with your position on the three questions above. Once there is agreement, RFC-0001 status moves from Draft to Accepted and Phase 2 engineering work can start.
Purpose
This is the focused discussion issue for RFC-0001: erp-agent.
The RFC was originally drafted as wasmagent-js#8 and has been migrated here since it spans multiple repos.
What needs a decision (Phase 1 scope)
RFC-0001 lists six open questions. The three that block Phase 1 are:
First ERP target — Odoo (recommended) or NetSuite? This determines which SDK, test environment, and verifier examples land in the PoC.
@wasmagent/worker-template— extract now or later? RFC recommendation is later (copy bscode first, extract after two repos prove the pattern). Any objections?Repo visibility — public from day one (matches bscode) or private until the PoC is presentable?
Not in scope here
@wasmagent/erp-verifiersvs in-repo) — can wait until Phase 2How to engage
Comment with your position on the three questions above. Once there is agreement, RFC-0001 status moves from Draft to Accepted and Phase 2 engineering work can start.