Skip to content

aRcHmaGe333/AllDone

Repository files navigation

AllDone

Closed-loop home provisioning built around reusable containers, return logistics, industrial washing, and recirculation.

AllDone is a concept and prototype project for replacing repetitive household shopping with a managed supply loop. Goods arrive in reusable containers, quantities adapt over time, and containers are collected, washed, refilled, and returned to circulation.

Reusable glass is the default planned consumer-facing container standard.


What AllDone is

AllDone is not just a delivery app.

It is a broader operating model:

production -> packaging -> circulation -> home supply -> return -> reuse

The project is aimed at recurring household needs such as:

  • groceries and prepared food
  • hygiene products
  • household consumables
  • other goods that fit a managed return-and-reuse loop

Why it matters

The current retail model wastes:

  • consumer time
  • packaging
  • transport effort
  • food through mismatch and overbuying
  • labor through fragmented shopping and last-mile behavior

AllDone is designed to remove that chore layer rather than slightly optimize the same disposable system.

Current repo status

This repository is public and presentable as:

  • a concept repo
  • a research repo
  • a prototype repo
  • an authorship and IP-claim record

It is not yet a pilot-ready operating business. The repo is explicit about that, and the remaining gaps are documented.

Recommended framing:

  • public exposure: yes
  • funding readiness: yes, at an early/pre-seed narrative level
  • pilot readiness: not yet

See docs/EXTERNAL_POSITIONING.md. All outward-facing text should also pass docs/EXPOSURE_GATE.md.

Prototype code

The current codebase contains an early backend prototype for:

  • household consumption profiling
  • quantity adjustment logic
  • simple schedule generation
  • reusable container circulation modeling
  • operator-facing household, subscription, route, wash, and billing workflow scaffolding
  • local file-backed runtime persistence

Local requirements:

  • Node.js 18+

Minimal local run path:

npm install
npm start

Optional demo run with sample data:

npm run demo:api

Prototype API entrypoint:

Prototype API surfaces:

  • /api/distribution
  • /api/operations

Persistence note:

Reading path

Start here:

  1. docs/DOCUMENT_GUIDE.md
  2. docs/INVESTOR_OVERVIEW.md
  3. docs/VALUE_PROPOSITION.md
  4. docs/EXTERNAL_POSITIONING.md
  5. docs/EXPOSURE_GATE.md
  6. docs/ARCHITECTURE_OVERVIEW.md
  7. docs/API_QUICKSTART.md
  8. docs/PILOT_MODEL_AND_ASSUMPTIONS.md
  9. docs/PILOT_UNIT_ECONOMICS.md
  10. docs/TOTAL_SYSTEM_VALUE_MODEL.md
  11. docs/FUNDRAISING_READINESS.md
  12. docs/TASKS.md

Public investor-pack structure:

Core decisions:

Supporting technical notes:

Project priorities

The immediate work is not "more features in the prototype."

The immediate work is:

  1. lock the first pilot container set
  2. define the wash and return operating model
  3. build defensible pilot economics
  4. implement the software required to run the loop

Intellectual property and verification

This work is published under the IPClaim APC License v1.1.

Authorship is supported by cryptographic timestamp records in .timestamps/.

The latest proof chain has been refreshed for the current public AllDone publication state. See LICENSE.md and VERIFY.md.

Contact

For collaboration, licensing, pilot partnerships, or investment inquiries:

Support

Ko-fi


We source it, pack it, bring it, collect it, and reuse it. You just use it.

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors