Hierarchy
AIFlare uses a 3-level hierarchy: Organization → Team → Project.
Organization (Org)Top-level group representing a company or organization
TeamTeam-level group under an Organization
ProjectUnit where actual work happens, nested under a Team
Capture & Timeline
Each commit maps to one Timeline Entry. A Hook triggers a Skill, which calls the capture API.
Work SessionOne Claude Code CLI session grouping multiple commits
Timeline EntryRecord unit per commit containing intent, summary, and conversation
Context Capturepost-commit hook triggers Skill to send metadata via API
Auth & Keys
Web uses JWT Bearer tokens; CLI uses API Keys.
JWT TokenBearer token used for web dashboard authentication
API KeyProject key for CLI/Hook auth, stored in aiflare.yml
Roles & Permissions
7 RoleTypes bound to ORG / TEAM / PROJECT scopes.
RoleType7 types: ORG_ADMIN, TEAM_ADMIN, PROJECT_ADMIN, and member/viewer variants
ScopeTypeScope where a role applies: ORG / TEAM / PROJECT
UserScopedRoleEntity managing permissions via (userId, scopeType, scopeId) tuple
Integrations
Three integration types: Hook, Skill, and MCP Server.
HookScript auto-executed on git post-commit / pre-push
SkillReusable script executed by Claude Code via slash command
MCP ServerExternal data server protocol providing context to Claude Code