Skip to content

association rules #11

@matt-beanland

Description

@matt-beanland

Develop some association rules that:

  • meet our lore/values
  • give people a clear view of their and others current standing
  • can be implemented by a membership system
  • issue membership artefacts

Not this ticket, but a an Association system would:

  • be in association repo
  • would use Ash, AshNeo4j, Artefactory, etc
  • would issue/store kinship Artefacts
  • would maintain membership
  • would keep diffo-dev in right relationship with regulator
  • would keep diffo-dev councillors, core, members, supporters in right relationship
  • would track candidate members
  • would have history
  • would manage subscriptions
  • would support declarations
  • would support imperatives
  • would run in cloud on hugging face.
  • would be a web app, maybe ash_typescript or hologram
    Must include a subscription payments system.
    Would run continuously supporting declarations and imperatives.
    Would implement the rules of the association.

idea is to have an online membership system for 'right' relationship
a 'recognise' system
willingness to be next inner (grant), recognition (acceptance) - these are declarations
we also have vacancy signalled, which can be accepted by a candidate, recognising them as next shell inner.

idea is that we have fixed periods

founder - forever?
council - yearly
core - monthly
member - weekly

inner is member of outer. subscription is in advance at current level.
if asked to step up, subscription moves to next shell at you next period
subscription always billed at weekly at current level maintain right relationship.

you can choose you support level, there is a minimum set by next inner shell.

idea is that supporters (not members) who aspire to be members can subscribe, and may join based on grant/vacancy.

Shell will generally choose who joins based on needs, given Dunbar, relationships are expensive, also mutual.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions