Technology Charter
Generated {{ new Date().toLocaleDateString("en-US", { year: "numeric", month: "long", day: "numeric", }) }}
Purpose
This charter guides our cooperative's technology decisions based on our shared values and operational needs. It ensures we choose tools that support our mission while respecting our principles of autonomy, sustainability, and mutual aid.
Core Principles
- → {{ principles.find((p) => p.id === principleId)?.name }}
Non-Negotiable Requirements
Any vendor failing these requirements is automatically disqualified.
- → {{ principles.find((p) => p.id === principleId)?.name }}
Technical Constraints
- → Authentication: {{ authOptions.find((o) => o.value === constraints.sso) ?.label }}
- → Hosting: {{ hostingOptions.find( (o) => o.value === constraints.hosting )?.label }}
- → Required Integrations: {{ constraints.integrations.join(", ") }}
- → Support Level: {{ supportOptions.find( (o) => o.value === constraints.support )?.label }}
- → Migration Timeline: {{ timelineOptions.find( (o) => o.value === constraints.timeline )?.label }}
Evaluation Rubric
Score each vendor option using these weighted criteria (0-5 scale):
| Criterion | Description | Weight |
|---|---|---|
| {{ weight.name }} | {{ weight.rubricDescription }} | {{ principleWeights[weight.id] }} |
Decision Heuristics
- → Any vendor failing a non-negotiable requirement is automatically eliminated
- → Prefer open standards and clear data export over feature abundance
- → When scores are within 10%, choose based on alignment with cooperative values
- → Document all decisions in the Vendor Decision Log for transparency
Procurement Process
- Identify need through collective discussion
- Research 3-5 potential vendors/solutions
- Eliminate any failing non-negotiables
- Score remaining options using rubric
- Trial top 2 options if possible
- Make collective decision with documented rationale
- Create migration/exit plan before commitment
Review & Accountability
- → Review this charter annually at minimum
- → Audit existing tools against charter quarterly
- → Document any exceptions with clear justification
- → Share learnings with other cooperatives in our network