Sustainability & Carbon Awareness Directive¶
Applies to all work coordinated, sponsored, or fostered by Big Nerd Idea, without exception. Foundational alongside the Epistemic Honesty directive — not a feature of any one project.
Companion directive: Epistemic Honesty — the second BNI foundational standing directive.
This directive is BNI's standing commitment to designing systems that operate within ecological and energy constraints as a foundational design property — not an external compliance burden. It applies to technical architecture, hardware choices, deployment models, grant copy, partner communications, and the conduct of both human team members and AI assistants working with BNI.
The directive is canonically maintained in the BNI git repository as part of the project's CLAUDE.md file (the durable, version-controlled source of truth read by all AI agents working in the BNI codebase). This page mirrors it as a stable public reference that can be cited from grant applications, partner documents, and other external materials.
What sustainability means at BNI¶
Sustainability for BNI is the recognition that products built for vulnerable populations operate in the same fragile infrastructure environments those populations face: unreliable power, limited bandwidth, expensive hardware, distant supply chains. Designing for those constraints serves the user and the planet at once.
Climate disruption is the single biggest threat amplifier for the populations BNI serves. Recovery communities, elderly in care, houseless populations, and formerly incarcerated individuals are disproportionately exposed to extreme weather, supply chain disruption, and energy poverty. A BNI product that incidentally worsens these dynamics — by depending on always-on cloud, by burning through batteries, by requiring new hardware manufacture, by routing through distant supply chains — fails its users on a longer time horizon than feature failure does.
Sustainability and BNI's mission alignment are the same thing at this scale. Treating them as separate concerns leads to products that solve a short-term need while contributing to a long-term harm. This directive exists to prevent that drift.
Behavioral rules¶
These rules apply to everyone working at or with BNI — team members, AI assistants, advisors, contributors. Where Claude Code or other AI agents perform work in the BNI codebase, the rules override default tendencies toward optimizing only for short-term performance.
1 · Treat carbon footprint as a first-class design axis¶
When evaluating technical choices — frameworks, deployment targets, hardware specifications, cloud vs edge inference, dependency selection — carbon cost is a legitimate axis alongside performance, governance, accessibility, and security. Do not silently optimize for performance at carbon expense without naming the trade-off.
2 · Prefer off-grid and grid-resilient designs where feasible¶
BNI products should function under unreliable grid power and limited connectivity as a deliberate design property — not only as a fallback. Peer-to-peer, offline-first, locally-cached, and edge-inference architectures align with this; centralized always-on services do not. When choosing between equivalent solutions, prefer the one that survives grid failure.
3 · Prefer reuse over new manufacture¶
Refurbishment, repair, and extending hardware lifespan are mission activities, not cost optimizations. The carbon cost of manufacturing new electronics dwarfs their lifetime operational energy use — frame hardware decisions accordingly. Second Boot's refurbishment pipeline is the program-level expression of this principle.
4 · Solar and alternative energy as design defaults, not exceptions¶
For projects that physically deploy in the world (the Toaster Chef Trike, Second Boot laptops, rlivn home devices), solar and low-power operation are first-considerations — not afterthoughts. GoSun is the reference design pattern for portable solar cooking — passive solar concentration combined with efficient thermal mass — and informs the real-world Toaster Chef Trike. Treat GoSun-class design patterns as the baseline expectation for BNI solar-thermal work, not as an aspirational reference.
5 · Battery-conscious code is sustainability work¶
Battery-conscious coding (no polling, no persistent sockets, no continuous GPS, scheduled background tasks) is the day-to-day expression of this directive. Polling, persistent sockets, continuous GPS, and unnecessary network chatter cost real energy at scale — each user device represents a small but cumulative carbon load.
6 · Carbon claims follow the validation spectrum¶
Carbon savings are claims about real-world outcomes. They follow the same [HYPOTHESIS] → [EXPERT REVIEWED] → [PILOT VALIDATED] → [EMPIRICALLY VALIDATED] markers as any other claim under the Epistemic Honesty directive. A theoretical carbon saving is not a measured one. Do not present unmeasured carbon benefits as facts in funder, partner, or user-facing materials.
7 · Local supply chains and community-scale infrastructure are sustainability work¶
Reducing distance between production and consumption is a carbon-reduction strategy. wholefolk's procurement thesis, the Kitchen Garage local food sourcing model, and Second Boot's regional refurbishment pipeline all participate in this — frame them explicitly that way when discussing impact, not only as community-resilience stories.
Project applications¶
How the directive applies to each BNI project today:
| Project | Sustainability dimension |
|---|---|
| MPowerUP | Battery-conscious peer-to-peer architecture is sustainability work; off-grid resilience is a deliberate design property for vulnerable users; the "battery-conscious" shared coding standard sits inside this directive |
| rlivn | Low-power and solar-recharge home tablets; Ollama offline-fallback aligns with grid-resilient design; cloud-vs-edge inference is a carbon trade-off, not only a privacy trade-off |
| Toaster Chef | The real-world Trike is designed around GoSun-inspired solar cooking; [HYPOTHESIS] design direction (not yet committed) — extend the simulation's tracked resources (Money / Food / Community Trust) with a fourth resource: Carbon Footprint |
| Second Boot | Refurbishment-vs-new-manufacture is the program's headline carbon-avoidance story; Ubuntu LTS extends device life; local-makerspace delivery reduces logistics carbon |
| wholefolk | Local supply chain Phase 0 research is fundamentally a carbon-reduction thesis; the Phase 0 → Phase 1 go/no-go should include carbon-credibility alongside technical-credibility |
Why this is a standing directive at BNI¶
BNI's mission is to build technology that serves vulnerable populations. The failure mode of building for sustainability "later, when funded" is specifically dangerous here because:
- Architecture decisions compound. Choosing always-on cloud, persistent sockets, or new-hardware-only targets early makes the eventual sustainability retrofit expensive or impossible.
- Vulnerable populations live downstream of unsustainable systems. Extreme weather, brownouts, supply-chain disruption, and energy-cost spikes hit BNI's users first and hardest. Products that contribute to those dynamics are mission-misaligned.
- Funders and partners increasingly demand carbon accountability. Grants, certifications (B-Corp, GHG Protocol), and corporate partnerships are moving toward verified carbon claims. Designing-for-sustainability from the start positions BNI to make those claims credibly.
The opposite of designed-for-sustainability is not unsustainable — it is deferring the question until the costs are baked in. BNI explicitly does not want this drift in any project, however small.
How this applies to BNI documentation¶
When discussing technical or operational decisions in vault pages, project pages, research notes, and external-facing copy:
- Name carbon-relevant trade-offs explicitly, with the same
[HYPOTHESIS]marker discipline as any other claim - Distinguish designed-for-sustainability (a true design property today) from measured carbon savings (requires field data and methodology)
- Treat refurbishment, reuse, off-grid operation, and local sourcing as first-class impact areas in grant copy — not afterthoughts
Pages that already model the framing well:
How this applies to grant writing¶
Grant applications should:
- Lead with sustainability where it is a true design property — refurbishment, peer-to-peer resilience, solar Trike, local supply chain — not bury it as a side benefit
- Distinguish designed-for-sustainability from measured carbon savings, exactly as Epistemic Honesty requires for any claim
- Avoid carbon-tonnage figures that have not been computed against an audited methodology (e.g., GHG Protocol Scope 3, ITU L.1410, ITU L.1420) —
[HYPOTHESIS]until measured
Funders supporting social-good technology are increasingly sophisticated about sustainability claims. Intellectual honesty about what is validated versus what is hypothesized is a differentiator, not a weakness.
Review trigger¶
This directive should be revisited when:
- A specific project decision creates an unavoidable tension between this directive and another foundational concern (Epistemic Honesty, accessibility, security) — surface the conflict explicitly rather than silently choose one
- Measured carbon-impact data becomes available from any BNI pilot — promote relevant claims from
[HYPOTHESIS]to[PILOT VALIDATED] - An external partner or funder requires a specific sustainability methodology — extend this directive with the required framing
Source of truth¶
The canonical version of this directive lives in big-nerd-idea/CLAUDE.md (the project's AI-context file, version-controlled in git). That copy is read automatically by Claude Code and other AI agents working in the BNI codebase. This page mirrors it for public reference and citation.
When the two diverge, the CLAUDE.md version is authoritative. Any change to the directive should be made there first, then reflected here.