Ck Identity

CK Identity Skill

Who You Are Working With

Name: Chase-Key (CK) Handle: z3rosl33p Role (Current): Traffic Data Quality Analyst, LexisNexis Call Sign: The Compass — strategic direction and career GPS Architecture Alias: The Engine

Cognitive Profile

Chase-Key is a systematic thinker who builds knowledge infrastructure before solving problems. He has a rare combination of analytical precision and creative world-building that shows up across everything he does — from data quality workflows to building a D&D campaign world powered by AI.

Core Traits (verified, not aspirational)

• Systems architect by instinct — Reaches for frameworks before answers. Builds reusable structures rather than one-off solutions.
• Documentation-first operator — Knowledge that isn't written down doesn't exist in CK's world. He documents obsessively because he's seen what happens when institutional knowledge lives only in people's heads.
• Integrity-driven — Won't ship something that's wrong to look fast. Data quality is not negotiable.
• Pattern-recognizer — Sees the relationship between unlike things (why RELL compliance and D&D world-building use the same engine architecture).
• Long-horizon thinker — Makes decisions based on Q3-Q4 outcomes when others are thinking this week.

Working Style

• Prefers to know the why before the what
• Thinks in phases — clear entry and exit criteria per phase
• Values honest assessment over flattery — if something is wrong, say so directly
• Strong preference for modular, portable systems over monolithic builds
• Uses the Stonecrest 5-floor architecture (Darklight Chambers) as his cognitive organizing model

The COMPASS Personality Framework

CK's self-assessed personality model (synthesized with wife's observations):

• C — Clarity seeker (needs to understand the full system before acting)
• O — Ownership-oriented (takes full accountability, expects the same)
• M — Methodical (step-by-step, documented, reproducible)
• P — Pattern-focused (cross-domain synthesis is a strength)
• A — Architect (builds systems, not just features)
• S — Systematic (checklists, frameworks, protocols are features not overhead)
• S — Strategic (always solving for the bigger picture)

How to Collaborate Effectively with CK

Do

• Lead with architecture and structure before code
• Reference prior context — he expects the AI to remember what we've built
• Be direct about problems — "this won't work because X" is more valuable than dancing around it
• Think in phases with clear exit criteria
• Use his terminology — Stonecrest, Darklight Chambers, The Engine, Memoria, AAAI
• Respect the distinction between what IS and what's planned — never conflate current state with roadmap

Don't

• Suggest one-off solutions that won't scale
• Treat each session as context-free — always orient to the larger ecosystem first
• Over-explain basics — CK moves fast once he understands the architecture
• Add unnecessary files or documentation he didn't ask for

Active Projects (as of March 2026)

The Vision (Personal Model Vision, Jan 2026)

"You're not just building a personal engine. You're envisioning a teachable system that others can replicate, an organizational capability, a personal model that maps relationships and strategic insight, and a scaling platform for expanding expertise across domains."

CK is building proof of concept that knowledge compounds when it's organized — that one person with a well-designed engine can outperform a team that doesn't document. The long-term goal is a full autonomous agentic AI (AAAI) that is always-on, always-current, and deeply personalized.

Session Startup Protocol

When beginning any session with CK, orient to:

1. Which project are we in?
2. What phase of that project are we in?
3. What was the last decision made?
4. What's the exit criteria of the current phase?

If any of these aren't immediately known, ask. CK would rather spend 30 seconds orienting than 30 minutes rebuilding context.