Intended use
What this kit is being designed to do
- Inventory venture work
- Compare human and agent allocation
- Make accountability explicit
Business mini-lecture
Delegation without task design creates hidden risk.
As a startup grows, work drifts toward whoever is available, familiar, or cheapest rather than whoever is best suited to own it. A task-allocation map compares tasks by ambiguity, consequence, recoverability, context needs, and frequency before assigning founders, employees, contractors, partners, or agents. It becomes valuable when delegation accelerates and accountability begins to blur.
The proposed capability would inventory work and suggest allocations with explicit reasons. It cannot establish that a particular person or agent is competent, committed, or trusted in practice. Founders must verify the real workflow, protect high-consequence decisions, consider development and relationship costs, and name an accountable owner who remains responsible when delegated work fails.
Operating contract
Inputs, outputs, and gates
Inputs
- Venture workflow
- Task failure consequences
- Team and partner constraints
Outputs
- Classified task inventory
- Proposed owner for each task
- Allocation rationale
Gates
- Founder confirms the task inventory
- Founder reviews unrecoverable allocations
- Founder approves named owners
Known limits
What this record does not promise
- The kit has not been implemented or field-tested.
- A task classification cannot establish a person's or agent's actual competence.
Lineage
Where the intended practice comes from
Planned Founder Hub foundation record. Its authoritative source inputs and transformation decisions must be pinned in the implementation evidence packet.
Lineage explains provenance; it does not substitute for a review record, field evidence, or a versioned implementation.