My Knowledge Hub
The team

ALEPH · Ecosystem scaling · Proposed role

Platform & Reliability Engineer

Make a growing ecosystem of applications reliable, secure and economical to operate—from the connections between them to the ability to recover when something fails.

ENGAGEMENT
Initially part-time / fractional, proposed
FOCUS
Hands-on platform operations
ACCOUNTABILITY
Christophe approves commitments and access

Draft job description—not a confirmed vacancy. Compensation, hours, location and contractual terms remain to be agreed.

01 · The mission

ALEPH is the strategy and context hub for an ecosystem of personal and business applications. This role supplies the practical engineering and operational ownership needed to scale that ecosystem—not another layer of strategy.

Start by making existing connections dependable and recovery demonstrable. Add capacity and shared services only where measurements and business needs justify them. Work with application owners rather than replacing their product responsibilities.

02 · What you will own

Reliable application connections

Implement and maintain APIs, MCP and OAuth connections. Handle token renewal, retries, timeouts and duplicate requests safely; make failures visible and traceable.

Safe delivery

Maintain repeatable deployment and release procedures, environment separation, automated checks and rollback plans. Preserve existing data and references during approved changes.

Monitoring & incident response

Establish useful service-health, error and performance signals. Create actionable alerts, incident runbooks and evidence-backed reviews of failures.

Backups & recovery

Document backup coverage and retention, verify backup completion and demonstrate restoration in an approved isolated environment. Record evidence and agreed recovery objectives.

Capacity & operating costs

Measure bottlenecks and usage before recommending changes. Plan for growing traffic, data and AI workloads; track hosting, storage, integrations and AI costs against agreed budgets.

Shared foundations

Reduce duplicated infrastructure where justified. Maintain clear service ownership, integration contracts and operational documentation without blurring application responsibilities.

03 · Essential experience

  • Hands-on operation of production web applications, including deployment, monitoring, incidents and rollback.
  • Practical API integration and OAuth experience, including least-privilege access and secure credential handling.
  • Database migrations, backup validation and tested recovery procedures.
  • Performance diagnosis, capacity planning and cost-aware infrastructure decisions.
  • Automated testing, CI/CD and clear, usable operational documentation.
  • Ability to communicate evidence, uncertainty and trade-offs in plain language.

04 · Useful additional skills

  • TypeScript, React, TanStack Start and edge-hosted applications.
  • Lovable Cloud, PostgreSQL and row-level access controls.
  • MCP integrations, AI workflow observability and usage-cost controls.
  • Experience keeping a small, multi-application environment maintainable without unnecessary complexity.

Proven operational judgement matters more than familiarity with every tool in the ecosystem.

05 · Working with the team

The engineer executes approved work. These personas provide advice, coordination and review; they are not autonomous operators or substitutes for human accountability.

Silver king chess piece leading five specialist pieces
Aleph

Sets ecosystem direction and application ownership.

Silver compass, gears and a labyrinth blueprint
Daedalus

Leads technical scaling proposals and architecture trade-offs.

Silver owl and orderly planning papers
Athena

Coordinates priorities, owners, dependencies and delivery.

Aegis’s silver shield guarding an application ecosystem
Aegis

Reviews security, privacy, access and recovery risks.

Silver many-eyed watchman's mask beside an inspection ledger and magnifying glass
Argus

Independently verifies results and cross-application workflows.

Ares’s warrior helmet and exploration map
Ares

Validates the business and product opportunities driving growth.

Mercury supports partner correspondence; Calliope keeps communication clear and consistent. Christophe retains final approval of budgets, commitments and sensitive changes.

06 · Proposed first outcomes

  1. Establish the baseline. Map services, owners, connections, access, costs and current reliability gaps. Separate confirmed evidence from unknowns.
  2. Prove safe operation. Produce backup and isolated restore evidence, critical integration checks, monitoring and approved release/rollback runbooks.
  3. Prepare measured growth. Present a prioritised scaling plan with capacity evidence, cost scenarios, dependencies and verification criteria.

07 · How success is judged

Reliable critical connections, repeatable recovery, observable failures, safer releases and a clear operating-cost baseline. Set measurable targets after the initial assessment; Argus independently verifies delivered outcomes.

08 · Authority & boundaries

Use only explicitly granted access. Production changes, spending, permission or credential changes, active security testing and external commitments require explicit approval. Protect private data and secrets; preserve existing data, immutable references and audit history. Do not treat an AI recommendation as authorisation.