# =============================================================================
# COMPETENCY RECORD - Cedric Ancellin's demonstrated engineering skills and
# experience. Third-party technologies and vendors are named as the concrete
# skill surface. Professional background / track record.
# =============================================================================

# ============================================================
# TECHNICAL LEADERSHIP - COMPETENCY RECORD
# ============================================================
# Core Purpose:
#   Demonstrated experience leading engineering as a founding
#   CTO / principal architect: owning architecture end to end,
#   setting and enforcing standards, reviewing and mentoring,
#   and supervising delivery of a design to completion.
# ============================================================

summary: >
  Led engineering as a founding CTO and principal architect -
  owning the architecture of the entire platform, setting the
  conventions and platform laws the codebase runs on, and either
  implementing directly or architecting and supervising engineers
  to deliver against that design and review.


# ==================================================================
# 1. ARCHITECTURE OWNERSHIP
# ==================================================================

architecture_ownership:
  description: >
    Owns the design of every layer of the platform and how the
    layers fit together.
  scope:
    - "Request engine, data layer, commerce/inventory, payments, integrations, warehouse, security, frontends, identity, and AI tooling."
    - "The cross-cutting decisions, multi-tenancy, environment model, statelessness, encoding schemes, soft-delete/audit conventions, that every domain inherits."
  approach: "Designs for a large team and a long-lived codebase: convention over magic, thin handlers over fat controllers, primitives over duplication, documented invariants over tribal knowledge."


# ==================================================================
# 2. STANDARDS & PLATFORM LAWS
# ==================================================================

standards:
  description: >
    Codified the standards and laws that keep a very large
    codebase coherent and safe.
  examples:
    - "Deployment law: all changes ship via version control + a publish pipeline; deployed paths are never edited directly."
    - "Data-access conventions: routed database codes, primary/replica tiers, entity-tracking for tracked schemas."
    - "Parameter-declaration discipline: request params must be declared per endpoint, never read ad hoc."
    - "Sandboxing + editing laws for AI and human contributors alike."
  medium: "A single authoritative repository guide plus a machine-readable knowledge base, so standards are discoverable and enforceable rather than folklore."


# ==================================================================
# 3. CODE REVIEW & QUALITY
# ==================================================================

review_quality:
  description: >
    Sets the quality bar through review and structural guardrails.
  practices:
    - "Reviews changes against documented conventions and invariants."
    - "Prefers structural prevention (single-writer models, checksums, idempotency, allowlists) over one-off fixes."
    - "Tracks follow-up/hardening work distinctly from immediate corrective fixes, with ownership and due dates."
    - "Uses a machine-readable anomalies/enhancements registry to keep known gaps visible."


# ==================================================================
# 4. DELIVERY SUPERVISION & MENTORSHIP
# ==================================================================

delivery:
  description: >
    Delivers through a mix of direct implementation and
    architect-and-supervise.
  model:
    - "Designs the solution, then either builds it or hands a precise design to an engineer and reviews to completion."
    - "Retains ownership of the design, the trade-offs, and the outcome regardless of who types the code."
    - "Mentors through explicit conventions, source-anchored documentation, and review feedback."
  breadth: "Coordinates work spanning backend, data engineering, frontend, security, and operations from a single coherent architectural vision."


# ==================================================================
# 5. STRATEGIC & CROSS-FUNCTIONAL SCOPE
# ==================================================================

strategic:
  description: >
    Operates beyond code into product, security, and data strategy.
  scope:
    - "Translates product and partner requirements into platform capabilities and phased delivery plans."
    - "Owns the security program end to end, controls registry, pentest remediation, incident response."
    - "Owns the data strategy, warehouse model, tenant data sharing, governance."
    - "Owns the AI strategy, knowledge-as-infrastructure and a governed AI-assisted development workflow."
  cross_reference:
    $ref: "https://zc8.com/overview"