business-depo/docs/specs/o1-package-structure.md

O1 Package — Structure & Phase-1 Pilot (DRAFT)

The first business-in-a-box: consignment refurbished-electronics arbitrage. Package id hitridge-business-o1.

Package tree

hitridge-business-o1/
├── manifest.json                 # the contract (spec v1.0)
├── modules/                      # layer 1: Odoo addon modules
│   ├── aura_business_core/       # generic venture core (schema, auth, layout)
│   └── hitridge_venture_o1/      # O1 models: seller, unit, order, warranty,
│                                 #   price-guide content, pipeline views
├── agents/                       # layer 2: neutral specialist cards + prompts
│   ├── o1-sellers-recruiter.json
│   ├── o1-test-operator.json
│   ├── o1-closer.json
│   └── o1-compliance.json
│   └── prompts/                  # external prompt markdown per agent
├── brain/                        # layer 3: runtime/memory
│   ├── brain.py                  # capability ships...
│   └── seeds/o1/                 # ...memories are EMPTY seeds at install
├── docs/                         # layer 4: business documents
│   ├── playbook.md               # O1 operating manual (90-day plan)
│   ├── agreement-template.odt    # BG consignment agreement
│   ├── test-checklist.md         # unit intake test + report template
│   └── price-guide-starter.md    # content engine seed
├── config/
│   ├── channels.json             # OLX/forums target list (BG)
│   └── pricing-rules.json        # intake→sale spread + price-drop ladder
├── install.sh                    # target-side verifier + installer (pull)
└── VALIDATE                        # output of validate-depo.sh (must pass)

Phase-1 pilot slice (what we build first)

Item	Contents	Acceptance
1. Manifest spec	manifest-spec.md frozen	validate-depo.sh accepts it
2. Agent-card spec	agent-card-spec.md frozen	validator rejects malformed cards
3. Converter	neutral card ↔ opencode md (both directions)	round-trip → identical hash
4. O1 skeleton	manifest + core module stub + 2 agents (sellers-recruiter, compliance) + docs stubs	package validates; 2 specialists runnable on THIS machine from neutral cards
5. Tool registry	names → implementations (odoo., file., script.run)	card tools resolve

Pilot deliberately ships 2 of 4 agents (sellers-recruiter, compliance) — they exercise the widest tool/memory/gate spread. test-operator and closer are added in phase 2 once the pipeline is proven.

Phase-1 acceptance (hard)

1. validate-depo.sh passes on hitridge-business-o1 (exit 0, no warnings).
2. Both pilot agents launch on this machine from the neutral cards (via converter → opencode), not from hand-written md.
3. Manifest round-trip: manifest.json → convert → convert back → identical.
4. No secrets in package (secrets_scan clean).
5. Nothing deployed anywhere — target install is phase 2.

Sequencing after pilot

• Phase 2: install.sh + target verification on a throwaway Odoo (Aura tower).
• Phase 3: depot repo (git + signed tags) + local mirror (depot-state.json).
• Phase 4: remaining agents + runtime/chat UI (Level 2 from earlier discussion).
• Phase 5: on-demand bridge sessions (MCP/API), default-disconnected.