selfdriven-octo
- 4 skills
- 0 followers
- 1 week ago last updated
- ▌ Software Developer · selfdriven-octoAbility to design, implement, test, deploy, and maintain software systems that meet defined requirements. Includes translating specifications into executable code, applying appropriate programming and design practices, managing changes over time, and operating software in production environments. Applies across application, platform, and infrastructure-adjacent contexts and is independent of specific languages, frameworks, or tools. Work may be performed individually or collaboratively and may be supported by automation or artificial intelligence, with human accountability retained for correctness, security, and outcomes.
- ▌ Selfdriven Ecosystem · selfdriven-octo bundleBuild selfdriven Foundation ecosystem properties — branded webapps, documents, APIs, and organisational frameworks. Use when the user mentions selfdriven, selfdriven.money, KERI/ACDC identity, Areas of Focus, Human Conductor models, or the selfdriven brand palette (flamingo #C8442F).
- ▌ Selfdriven Interactive Info Site Build · selfdriven-octoBuild selfdriven-branded interactive info websites from conceptual sketches, notebook photos, or framework descriptions. Use when the user wants to turn notes, sketches, diagrams, or conceptual frameworks into a polished single-file HTML interactive site with the selfdriven brand system — especially for KERI/ACDC trust architecture, digital interaction frameworks, or any selfdriven knowledge base content.
- ▌ Selfdriven Digital Interaction Framework · selfdriven-octoBuild content, webapps, and documentation based on the selfdriven Digital Interaction Framework — the layered trust architecture for digital relationships. Use when the user mentions trust layers, digital interaction framework, relationship lifecycle, agent network, trust tiers, policy stacks, risk calibration, transactional vs interactional, fidelity/confidence/provenance, or Architecture Decision Records (ADRs) in the selfdriven context.