akif/arclet-boards

Arclet Boards — private Kanban workspaces with AppID, DataK3, shared web and MCP actions.

A remix template · 1 remixes · Remix akif/arclet-boards

SUBMISSION.md

Freelancer Contest #2799133 submission

Mandatory public Dodil Git repository: https://git.dodil.io/akif/arclet-boards

Live application: https://arclet-boards-akif-8080.ignite.dodil.cloud

Application MCP endpoint: https://arclet-boards-akif-8080.ignite.dodil.cloud/mcp

Arclet Boards gives teams a clear, private space for their next step. It offers workspaces, board-specific roles, ordered lists, real draggable cards, descriptions, labels, member assignment, due dates, checklists, and complete card activity. The responsive web application and action-oriented MCP endpoint call the same authorized application layer.

All persistent application data lives in DataK3; AppID authenticates people; Ignite hosts the application; Dodil Git CI tests, builds and deploys it. The repository is MIT licensed and includes a complete remix manifest and schema. README.md documents the post-remix email verification and callback checks.

For verification details and honest limits, see STATUS.md and evidence/. Unit tests, actual DataK3 persistence checks, and real deployed user/API/MCP isolation checks are kept distinct. Screenshots supplement the repository and never replace it as the submission.

Five honest notes

  1. The starter was preserved and inspected before implementation; its platform integrations were carried forward rather than replaced with another cloud.
  2. Windows/Python 3.14 exposed a starter dependency conflict, resolved with exact compatible FastAPI, MCP, Starlette and psycopg pins; CI runs Python 3.12.
  3. A deployed test caught Ignite's internal Host being used in OAuth metadata; the public forwarding header is now used and regression-tested.
  4. Email invitations are application grants, not pretend email delivery. Pool email verification is required before team invitations, and accepted grants bind to immutable AppID subjects.
  5. Verification claims are limited to recorded evidence. A valid remix plan is not described as a successful independent-organization remix.