Holo-REA 2020 strategic plan (ideation)

Going to close this thread for now. Lots of good info in here and things we might explore, but in light of global catastrophes all this planning is now moot!

CoMakery has a task system with the Kanban states Ready, Started, Approved, Paid. There's also an API. Let me know if someone wants to do an integration of reputation-data-modeals or REA. I can grant access to the private repo on GitHub.

Would love to, please send an invite!

Yeah. I'm chatting with Guillem tomorrow to build some form of co-ordination/collaboration. Join in if you'd like.

See also https://forum.holochain.org/t/4-maybe-nice-re-usable-zomes/2322 <3

Since this was posted we decided to build open-source libraries of reputation-data-modules. Co-ordination between these SC and HoloREA modules would be priority at this stage. I'll be speaking about it in our communication across channels.

These are jobs that we can do (now) with groups in our ecosystem that will help to evolve Holo-REA as an offering. Wanted to share here as I think it’s a better place than the Gitbook… it’s probably already outdated! hah

“DNA integration” refers to a third-party, domain-specific Holochain application implementing its own backend logic which in some way interfaces with the REA data that Holo-REA Rust crates can provide.

“API integration” refers to a third-party application interfacing with one or more Holo-REA DNAs via the API bridge (ie. hc-web-client). The third-party app may be of any type (in-browser, client/server, any non-Holochain distributed system).

• Sacred Capital

  • DNA integration: REA data import as reputation

• CoMakery

  • Kanban board UI?

  • API integration: batches & tasks as REA proposals, intents & commitments

  • DNA integration: tokens as REA resources

• InvestorEngine

  • Kanban board UI

  • Value equations DNA

• DirectHarvest

  • Inventory management UI

  • DNA integration: produce as REA resources, exchanges as REA events

• BeefLedger

  • DNA integration: ResourceSpecification case study

• HoloFuel

  • DNA integration: accounting for tokens as REA resources

• Noosa Power

  • DNA integration: KW/h trading

• RedGrid

  • DNA integration: KW/h trading

• Humm

  • DNA integration: tracking of article payments (via Stripe)

Any and all other suggestions welcomed!

General thoughts: I think the "go with the flow" method wasn't that bad so far, and that working code was the critical path. Next phase work with a small number of projects to get a full stack working, maybe not more than 2, depending on their requirements? And as soon as a dogfooding opportunity arises, definitely do that. I don't think we can work with very many use cases at one time yet, there will be a lot of wrinkles to iron out technically, and experimentation on what it means to be a framework. So the first group(s) need to be very willing to be our partners in development, and understand they are contributing to Holo-REA at the same time as we are contributing to their project. I don't see that we are quite ready to do a blitz for more user groups, although some more trained devs would of course be nice. (Assuming that one or two of the groups we are talking to want to move forward.)

Thanks. This is great. Also helps me calibrate Sacred Capital's strategy accordingly. I'll add feedback as it emerges.

@Emaline we've talked to Matslats off and on over the years about REA and his work, and a few months ago did a mapping between ValueFlows and Credit Commons, in the context of supporting the Mutual Aid Network. They integrate nicely - what we found was that a lot of his api could be changed to VF terminology, with some left-overs. I thought it might be best to create a separate extension vocabulary for the mutual credit specific elements, and use that + VF for the Credit Commons. Nothing was implemented though, at least yet.

>perhaps it begins simply with mutual credit wallets!

Makes sense as a core place to start - group agents, credit transfers between members (economic events), member accounts/wallets (economic resources). Then add offers/requests (proposals, intents), maybe commitments, or just connect the transfers to the offers/requests.

The mutual credit specific stuff included rate conversions between groups so members could trade across groups, credit limit policy in a group, that kind of thing.