HR-ERP
llms.txt1 starsChanged 6 months agoApache-2.0View on GitHub
HR scaffold for testing T0–T4 agent governance on a multi-tenant SaaS fixture. ESS/payroll/benefits stay as a realistic blast-radius domain. Not a certified payroll vendor. Do not compete with ERPNext, Odoo, or OrangeHRM on HR features. Community and Copilot agents start at AGENTS.md. Factory/site overlay is docs/factory-overlay.md. Pair FidusGate for Cedar gates and runtime receipts — do not duplicate Cedar here.
In this repository37 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/agent-ai-governance.mdcCursor rule
- .cursor/rules/agent-architecture.mdcCursor rule
- .cursor/rules/agent-code-health.mdcCursor rule
- .cursor/rules/agent-db-migration-state.mdcCursor rule
- .cursor/rules/agent-developer-advocate.mdcCursor rule
- .cursor/rules/agent-devops-lifecycle.mdcCursor rule
- .cursor/rules/agent-finops.mdcCursor rule
- .cursor/rules/agent-integrations.mdcCursor rule
- .cursor/rules/agent-legal-hr-compliance.mdcCursor rule
- .cursor/rules/agent-mlops.mdcCursor rule
- .cursor/rules/agent-nextjs.mdcCursor rule
- .cursor/rules/agent-packaging-supply-chain.mdcCursor rule
- .cursor/rules/agent-qa.mdcCursor rule
- .cursor/rules/agent-security.mdcCursor rule
- .cursor/rules/orchestrator-hr-erp.mdcCursor rule
- .cursor/rules/repo-boundaries.mdcCursor rule
- .cursor/rules/site-contract.mdcCursor rule
- .cursor/rules/vercel-jwt-smoke.mdcCursor rule
- hr-contributor-handoffSkill
- hr-data-custodySkill
- hr-devops-lifecycleSkill
- hr-domain-boundariesSkill
- hr-foundation-governanceSkill
- hr-governance-learningSkill
- hr-human-collaborationSkill
- hr-orchestration-lanesSkill
- hr-product-gateSkill
- hr-product-mcp-governanceSkill
- hr-quality-labSkill
- hr-regulated-domainSkill
- hr-swarm-governanceSkill
- site-deliverySkill
- code-reviewSkill
- hr-data-custodySkill
The file
Files
# HR ERP > HR scaffold for testing T0–T4 agent governance on a multi-tenant SaaS fixture. ESS/payroll/benefits stay as a realistic blast-radius domain. Not a certified payroll vendor. Do not compete with ERPNext, Odoo, or OrangeHRM on HR features. Community and Copilot agents start at AGENTS.md. Factory/site overlay is docs/factory-overlay.md. Pair FidusGate for Cedar gates and runtime receipts — do not duplicate Cedar here. ## Docs - [Design pivot](docs/DESIGN-PIVOT.md): compete on governance, not payroll - [AGENTS.md](AGENTS.md): community contract, governance commands, never production payroll - [README.md](README.md): scaffold lead, two-layer table (harness first) - [Evergreen positioning](docs/meta/evergreen-open-source-positioning.md): fixture domain + FidusGate pairing - [Factory overlay](docs/factory-overlay.md): corporate/site gates - [Copilot instructions](.github/copilot-instructions.md): never-do rules - [Security](SECURITY.md): private advisories; synthetic data only ## Verify - `./scripts/harness/verify.sh` - `npm run governance:ci` ## Skills - [hr-data-custody](.github/skills/hr-data-custody/SKILL.md): Prisma/SQL and RLS-safe migrations — high-risk fixture domain, not a payroll product - [.github/copilot-instructions.md](.github/copilot-instructions.md): repository-wide Copilot coding standards - [.github/instructions/](.github/instructions/): path-specific Copilot coding standards (September 2026) - [.github/skills/code-review/SKILL.md](.github/skills/code-review/SKILL.md): Copilot code review skill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

