🏭📈 Nimble, market-driven, micro-factories. 🚧 Pre-alpha!
- Highly modular micro-markets for each service provider in a micro-factory.
- Markets drive efficiency
- Every component in the micro-factory is either material or a service provider.
- Current service providers types:
- Storage (e.g. shop floor)
- Transportation (e.g. human, conveyer, robot)
- Transmutation (e.g. FFF printer, laser cutter, milling tool)
- The whole system simulated in a Game like environment
- Cryptographically sign a runner or build request identity throughout the process building a history
- Services providers could become financially autonomous competitive objective maximising entities
- Desired emergent behaviour: trustless, competitive and nimble micro-transactions in the micro-markets of the micro-factory!
- Can we interface with:
- Identity using Texile for public/private key based system
- Payments API (fiat / crypto)
- Autonomous organisation systems (Aragon)
- Factory 'boundary services':
- Delivery services (DHL/UPS API etc.)
- Energy providers
- Typescript
- React (react-spring)
- Redux (redux-saga, reselect, redux-form)
- Three (react-three-fiber)
- IPFS / Textile for P2P storage and database
Following angular conventions
<type>(<scope>): <subject>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>
- Major (Breaking):
perf(XYZ): Description of XYZ
- Minor (Feature):
feat(XYZ): Description of XYZ.
orUpdate(XYZ): Description of XYZ
- Patch:
fix(XYZ): Description of XYZ
Everything is subject to radical change... (the ultimate vision of the project is still forming)
Issues, ideas and PRs welcome nevertheless.
This project was bootstrapped with Create React App.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build
folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject
, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject
at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject
will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject
. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.