FCS Architecture Reference

Constructs

The FCS protocol, and by extension the entire Catsup architecture, is derived from the following constructs:

• Account
  • Tied to a single login and has a username, with any number of identities (instances may cap this for sanity purposes). Identities are stored as children of the account, and the account is what joins a group.

• Identity
  • Stores within it the typical 'user' metadata including a message description link and its attached background. Each identity is associated with a parent group.

• Group
  • Contains metadata, may have children of any type (accounts will always belong to root group), has a parent (with exception of root group).

• Message
  • Contains contents, references to other messages, a reference to an identity, and a reference to media. The only required field is identity but at least one of the others should be expected.

ECS

The Entity Component System (essentially the mapping of one ULID to various characteristics) of catsup is as follows:

Accounts

An account ID can be expected to reference:

• A list of identities

Identities

An identity ID can be expected to reference:

• A message containing the description and background media of the identity

• A reference to a permissions bitfield

• A permissions bitfield

Groups

A group ID can be expected to reference:

Messages

A message ID can be expected to reference: