Create Core Concepts page/sub-pages

[smckeon-so]

Our target structure is as follows for the core concepts section. This section will pull content from many different place to summarize out code Aranya concepts

• Core concepts (break down into sub-pages)

  • Terminology section from overview.md

  • Architecture

    • Arch diagram
      • Breakdown of components from overview.md (do not separate by on-graph/off-graph; instead, combine into single list!)
    • Control plane/data plane from overview.md

  • Graph

    • Overview (combine contents from section in overview.md and those in https://git.spideroak-inc.com/spideroak-inc/aranya-docs/wiki/Our-Products%3A-Aranya#graph)
    • Policy (either combine contents from overview.md section and https://git.spideroak-inc.com/spideroak-inc/aranya-docs/wiki/Our-Products%3A-Aranya#policy, or use just the brief descriptions from overview.md here and place everything from the wiki page under "Access management" chapter)
    • Table comparing on-graph vs. off-graph from overview.md
    • On-graph
      • Adding commands to graph (combine sections on "calling an action" from overview and wiki doc)
      • Syncing (combine sections on "syncing" from overview and wiki doc)
        • Braid algorithm? (enough detail to understand its overall purpose)
      • Include flow diagram from https://git.spideroak-inc.com/spideroak-inc/aranya-docs/wiki/Our-Products%3A-Aranya#runtime-putting-it-all-together
    • Off-graph
      • Ephemeral commands (take from https://git.spideroak-inc.com/spideroak-inc/aranya-docs/wiki/Our-Products%3A-Aranya#ephemeral-sessionscommands and the aranya sessions "spec"?)
      • Indicate that ephemeral commands can be sent via any means to peers who can process/validate them and that we include a secure real-time data exchange which relies on ephemeral commands (include reference to "real-time data exchange" chapter)

  • Access management (Control Plane)

    • Policy (use content with code from wiki page here (?) and reference to "Policy" chapter for more details)
      • Default policy summary + reference
      • Default crypto
    • Entity/user/device
    • Custom roles (pending spec)
    • Revocation

  • Real-time data exchange (Data Plane)

    • Overview (from wiki doc)
      • References to "AFC" in wiki doc apply also to Quic channels, so just replace "AFC" with "Aranya channels" for general use
    • Creating a channel (combining from overview.md and wiki doc)
    • Sending data (combining from overview.md and wiki doc)
    • AFC vs. Quic channels
      • Mostly just underlying transport, but include how that leads to other differences (like cert management)
    • Channels crypto