Does this record reflect you?

{
  "employment_id": "EMP_CURRENT",
  "employer": "Fictional Fieldwork Ltd",
  "employer_of_record": "Fictional Fieldwork Ltd",
  "title": "Head of Engineering",
  "start": "2022-07",
  "end": "present",
  "parent_employment_id": "EMP_STAFF",
  "location": "London",
  "source_refs": [
    {
      "source_id": "SRC_SUBJECT",
      "excerpt": "Head of Engineering at Fictional Fieldwork Ltd, July 2022 to present. Leads a group of 18 engineers through three engineering managers; partners with product and operations. London."
    }
  ],
  "external_safe": false,
  "evidence_status": "self_asserted",
  "corroborators": [],
  "scope": {
    "team_size": "18 engineers",
    "direct_reports": "3 engineering managers",
    "source_refs": [
      {
        "source_id": "SRC_SUBJECT",
        "excerpt": "Head of Engineering at Fictional Fieldwork Ltd, July 2022 to present. Leads a group of 18 engineers through three engineering managers; partners with product and operations. London."
      }
    ]
  }
}

Context

Four product teams requested different platform improvements from the same small group.

Responsibility

Agree priorities and ownership within the available engineering capacity.

Recorded dates

From

2023-05

To

2023-05

Dates are approximate

No

Recorded measures

Nothing recorded

Skills

• engineering leadership
• prioritization

Outcome type

output

Corroborators

Nothing recorded

Constraints

Nothing recorded

{
  "id": "E_PLATFORM_ADOPTION",
  "title": "Chose an adoption plan within team capacity",
  "employment_id": "EMP_CURRENT",
  "occurred": {
    "start": "2023-05",
    "end": "2023-05",
    "inferred": false
  },
  "star": {
    "situation": "Four product teams requested different platform improvements from the same small group.",
    "task": "Agree priorities and ownership within the available engineering capacity.",
    "action": "Worked with engineering managers and product leads to compare support burden and migration effort.",
    "result": "The group agreed a two-quarter platform adoption plan and named an owner for each migration; revenue impact was not measured."
  },
  "metrics": [],
  "skills": [
    "engineering leadership",
    "prioritization"
  ],
  "source_refs": [
    {
      "source_id": "SRC_SUBJECT",
      "excerpt": "2023-05: Four product teams requested different platform improvements from the same small group. Agree priorities and ownership within the available engineering capacity. Worked with engineering managers and product leads to compare support burden and migration effort. The group agreed a two-quarter platform adoption plan and named an owner for each migration; revenue impact was not measured."
    }
  ],
  "evidence_status": "self_asserted",
  "external_safe": false,
  "outcome_type": "output",
  "corroborators": [],
  "constraints": []
}

Context

A supplier arrangement needed a confidential technical review.

Responsibility

Give procurement a technical assessment without disclosing internal contract details.

Recorded dates

From

2024-11

To

2024-11

Dates are approximate

No

Recorded measures

Nothing recorded

Skills

• technical due diligence
• stakeholder communication

Outcome type

output

Corroborators

Nothing recorded

Constraints

• Private supplier and employer context; do not reuse in external documents.

{
  "id": "E_PRIVATE_REVIEW",
  "title": "Led a sensitive supplier review",
  "employment_id": "EMP_CURRENT",
  "occurred": {
    "start": "2024-11",
    "end": "2024-11",
    "inferred": false
  },
  "star": {
    "situation": "A supplier arrangement needed a confidential technical review.",
    "task": "Give procurement a technical assessment without disclosing internal contract details.",
    "action": "Coordinated engineering and procurement input and wrote the technical tradeoff assessment.",
    "result": "Procurement used the assessment in its supplier review; commercial terms and the final decision remain private."
  },
  "metrics": [],
  "skills": [
    "technical due diligence",
    "stakeholder communication"
  ],
  "source_refs": [
    {
      "source_id": "SRC_SUBJECT",
      "excerpt": "2024-11: A supplier arrangement needed a confidential technical review. Give procurement a technical assessment without disclosing internal contract details. Coordinated engineering and procurement input and wrote the technical tradeoff assessment. Procurement used the assessment in its supplier review; commercial terms and the final decision remain private."
    }
  ],
  "evidence_status": "self_asserted",
  "external_safe": false,
  "outcome_type": "output",
  "corroborators": [],
  "constraints": [
    "Private supplier and employer context; do not reuse in external documents."
  ]
}

Context

The group wanted to reduce waiting for design reviews.

Responsibility

Understand the effect of the new review practice.

Recorded dates

From

2025-02

To

2025-02

Dates are approximate

No

Recorded measures

Nothing recorded

Skills

• engineering leadership

Outcome type

output

Corroborators

Nothing recorded

Constraints

Nothing recorded

Questions still open

• Can the baseline and measurement period be recovered?

{
  "id": "E_REVIEW_SPEED",
  "title": "Shortened design-review queues by 35%",
  "employment_id": "EMP_CURRENT",
  "occurred": {
    "start": "2025-02",
    "end": "2025-02",
    "inferred": false
  },
  "star": {
    "situation": "The group wanted to reduce waiting for design reviews.",
    "task": "Understand the effect of the new review practice.",
    "action": "Compared review queues informally.",
    "result": "Estimated that review queues became 35% shorter."
  },
  "metrics": [],
  "skills": [
    "engineering leadership"
  ],
  "source_refs": [
    {
      "source_id": "SRC_NOTES",
      "excerpt": "A draft February 2025 review estimated that design-review queues became 35% shorter. The original baseline and measurement period were not retained. The percentage must not be treated as an established outcome."
    }
  ],
  "evidence_status": "unresolved",
  "external_safe": false,
  "outcome_type": "output",
  "corroborators": [],
  "constraints": [],
  "open_questions": [
    "Can the baseline and measurement period be recovered?"
  ]
}

Context

The group was trying a shared approach to design reviews.

Responsibility

Help engineers learn from each other.

Recorded dates

From

2025-02

To

2025-02

Dates are approximate

No

Recorded measures

Nothing recorded

Skills

• coaching
• engineering leadership

Outcome type

output

Corroborators

Nothing recorded

Constraints

Nothing recorded

Questions still open

• What part of coaching was most useful to the engineers?

{
  "id": "E_STORY_2",
  "title": "Built an engineering practice",
  "employment_id": "EMP_CURRENT",
  "occurred": {
    "start": "2025-02",
    "end": "2025-02",
    "inferred": false
  },
  "star": {
    "situation": "The group was trying a shared approach to design reviews.",
    "task": "Help engineers learn from each other.",
    "action": "Personally designed the peer review format, hired the engineers and coached every engineer.",
    "result": "The engineering group adopted peer design reviews."
  },
  "metrics": [],
  "skills": [
    "coaching",
    "engineering leadership"
  ],
  "source_refs": [
    {
      "source_id": "SRC_SUBJECT",
      "excerpt": "In February 2025 I hired and coached engineers while introducing peer design reviews. The engineering group adopted peer design reviews."
    },
    {
      "source_id": "SRC_MANAGER",
      "excerpt": "Jules sponsored the peer design-review pilot and coached three engineering managers. Engineers Mara Vale and Theo Reed designed the review format together. Hiring was shared with the managers. The engineering group adopted peer design reviews; we have not collected feedback about which coaching was most useful."
    }
  ],
  "evidence_status": "self_asserted",
  "external_safe": false,
  "outcome_type": "output",
  "corroborators": [],
  "constraints": [],
  "open_questions": [
    "What part of coaching was most useful to the engineers?"
  ]
}

{
  "employment_id": "EMP_STAFF",
  "employer": "Fictional Fieldwork Ltd",
  "employer_of_record": "Fictional Fieldwork Ltd",
  "title": "Staff Engineer",
  "start": "2018-01",
  "end": "2022-06",
  "parent_employment_id": null,
  "location": "London",
  "source_refs": [
    {
      "source_id": "SRC_SUBJECT",
      "excerpt": "Staff Engineer at Fictional Fieldwork Ltd, January 2018 to June 2022. Supported several product teams without line-management responsibility."
    }
  ],
  "external_safe": false,
  "evidence_status": "self_asserted",
  "corroborators": []
}

Context

Product and operations disagreed about replacing a shared service in one release.

Responsibility

Make the migration tradeoffs explicit and agree a sequence the teams could support.

Recorded dates

From

2021-02

To

2021-02

Dates are approximate

No

Recorded measures

Nothing recorded

Skills

• software architecture
• stakeholder communication

Outcome type

output

Corroborators

Nothing recorded

Constraints

Nothing recorded

{
  "id": "E_SERVICE_BOUNDARIES",
  "title": "Agreed a gradual service separation",
  "employment_id": "EMP_STAFF",
  "occurred": {
    "start": "2021-02",
    "end": "2021-02",
    "inferred": false
  },
  "star": {
    "situation": "Product and operations disagreed about replacing a shared service in one release.",
    "task": "Make the migration tradeoffs explicit and agree a sequence the teams could support.",
    "action": "Mapped failure boundaries with both groups and authored a staged separation proposal.",
    "result": "The teams chose a staged separation and retained a rollback path; product teams implemented the changes."
  },
  "metrics": [],
  "skills": [
    "software architecture",
    "stakeholder communication"
  ],
  "source_refs": [
    {
      "source_id": "SRC_SUBJECT",
      "excerpt": "2021-02: Product and operations disagreed about replacing a shared service in one release. Make the migration tradeoffs explicit and agree a sequence the teams could support. Mapped failure boundaries with both groups and authored a staged separation proposal. The teams chose a staged separation and retained a rollback path; product teams implemented the changes."
    }
  ],
  "evidence_status": "self_asserted",
  "external_safe": false,
  "outcome_type": "output",
  "corroborators": [],
  "constraints": []
}

Context

Product teams needed to test deployment steps before changing production.

Responsibility

Make deployment practice repeatable without taking delivery ownership from the teams.

Recorded dates

From

2019-03

To

2019-03

Dates are approximate

No

Recorded measures

Nothing recorded

Skills

• platform engineering
• cross-team collaboration

Outcome type

output

Corroborators

Nothing recorded

Constraints

Nothing recorded

{
  "id": "E_STORY_1",
  "title": "Created a deployment rehearsal tool",
  "employment_id": "EMP_STAFF",
  "occurred": {
    "start": "2019-03",
    "end": "2019-03",
    "inferred": false
  },
  "star": {
    "situation": "Product teams needed to test deployment steps before changing production.",
    "task": "Make deployment practice repeatable without taking delivery ownership from the teams.",
    "action": "Designed the rehearsal format and co-built its runner with engineers.",
    "result": "Two teams adopted rehearsals before deployment."
  },
  "metrics": [],
  "skills": [
    "platform engineering",
    "cross-team collaboration"
  ],
  "source_refs": [
    {
      "source_id": "SRC_SUBJECT",
      "excerpt": "In March 2019 I designed a deployment rehearsal format and co-built its runner with engineers. Two teams adopted rehearsals before deployment."
    }
  ],
  "evidence_status": "self_asserted",
  "external_safe": false,
  "outcome_type": "output",
  "corroborators": [],
  "constraints": []
}

Context

A community event invited practitioners to discuss deployment practice.

Responsibility

Share the approach with peers.

Recorded dates

From

2021-06

To

2021-06

Dates are approximate

No

Recorded measures

Nothing recorded

Skills

• public speaking
• knowledge transfer

Outcome type

output

Corroborators

Nothing recorded

Constraints

Nothing recorded

{
  "id": "E_TALK",
  "title": "Shared deployment practice with peers",
  "employment_id": "EMP_STAFF",
  "occurred": {
    "start": "2021-06",
    "end": "2021-06",
    "inferred": false
  },
  "star": {
    "situation": "A community event invited practitioners to discuss deployment practice.",
    "task": "Share the approach with peers.",
    "action": "Co-presented with Mara Vale at Community Systems Forum.",
    "result": "The programme lists both speakers and the shared talk; audience impact was not measured."
  },
  "metrics": [],
  "skills": [
    "public speaking",
    "knowledge transfer"
  ],
  "source_refs": [
    {
      "source_id": "SRC_TALK",
      "excerpt": "Community Systems Forum, June 2021: \"Practising deployments before production\". Co-presenters: Jules Elm and Mara Vale, Fictional Fieldwork Ltd. The programme establishes the shared talk title and speaker listing, not audience size or impact."
    }
  ],
  "evidence_status": "self_asserted",
  "external_safe": false,
  "outcome_type": "output",
  "corroborators": [],
  "constraints": []
}

{
  "employment_id": "EMP_NORTH",
  "employer": "Fictional North Quay Systems",
  "employer_of_record": "Fictional North Quay Systems",
  "title": "Senior Software Engineer",
  "start": "2014-07",
  "end": "2017-12",
  "parent_employment_id": null,
  "location": "London",
  "source_refs": [
    {
      "source_id": "SRC_SUBJECT",
      "excerpt": "Senior Software Engineer at Fictional North Quay Systems, July 2014 to December 2017. Worked on service operations and shared platform tools."
    }
  ],
  "external_safe": false,
  "evidence_status": "self_asserted",
  "corroborators": []
}

Context

Teams had recovery instructions but had not practised making decisions together.

Responsibility

Help service owners and support staff rehearse escalation decisions.

Recorded dates

From

2017-10

To

2017-10

Dates are approximate

No

Recorded measures

Nothing recorded

Skills

• incident management
• facilitation

Outcome type

output

Corroborators

Nothing recorded

Constraints

Nothing recorded

{
  "id": "E_INCIDENT_EXERCISES",
  "title": "Practised incident decisions across teams",
  "employment_id": "EMP_NORTH",
  "occurred": {
    "start": "2017-10",
    "end": "2017-10",
    "inferred": false
  },
  "star": {
    "situation": "Teams had recovery instructions but had not practised making decisions together.",
    "task": "Help service owners and support staff rehearse escalation decisions.",
    "action": "Facilitated four incident exercises with service owners and support staff.",
    "result": "The group clarified escalation owners and recorded gaps in recovery instructions; outage reduction was not measured."
  },
  "metrics": [],
  "skills": [
    "incident management",
    "facilitation"
  ],
  "source_refs": [
    {
      "source_id": "SRC_SUBJECT",
      "excerpt": "2017-10: Teams had recovery instructions but had not practised making decisions together. Help service owners and support staff rehearse escalation decisions. Facilitated four incident exercises with service owners and support staff. The group clarified escalation owners and recorded gaps in recovery instructions; outage reduction was not measured."
    }
  ],
  "evidence_status": "self_asserted",
  "external_safe": false,
  "outcome_type": "output",
  "corroborators": [],
  "constraints": []
}

Context

Services needed visibility of their queues.

Responsibility

Make service health visible.

Recorded dates

From

2016-03

To

2016-03

Dates are approximate

No

Recorded measures

Nothing recorded

Skills

• observability

Outcome type

output

Corroborators

Nothing recorded

Constraints

Nothing recorded

{
  "id": "E_QUEUE_DUPLICATE",
  "title": "Built a service health dashboard",
  "employment_id": "EMP_NORTH",
  "occurred": {
    "start": "2016-03",
    "end": "2016-03",
    "inferred": false
  },
  "star": {
    "situation": "Services needed visibility of their queues.",
    "task": "Make service health visible.",
    "action": "Built a service health dashboard.",
    "result": "Five services adopted it."
  },
  "metrics": [],
  "skills": [
    "observability"
  ],
  "source_refs": [
    {
      "source_id": "SRC_SUBJECT",
      "excerpt": "March 2016: built a service health dashboard adopted by five services."
    },
    {
      "source_id": "SRC_NOTES",
      "excerpt": "The March 2016 queue-age dashboard and the \"service health dashboard\" in the resume are the same project. Jules designed the dashboard and worked with the five service owners on alert thresholds. This is not a second delivery."
    }
  ],
  "evidence_status": "self_asserted",
  "external_safe": false,
  "outcome_type": "output",
  "corroborators": [],
  "constraints": []
}

Context

Service teams could not distinguish a quiet queue from a stalled consumer.

Responsibility

Expose queue age and ownership without replacing the messaging platform.

Recorded dates

From

2016-03

To

2016-03

Dates are approximate

No

Recorded measures

Nothing recorded

Skills

• observability
• cross-team collaboration

Outcome type

output

Corroborators

Nothing recorded

Constraints

Nothing recorded

{
  "id": "E_QUEUE_VISIBILITY",
  "title": "Made a shared queue visible to service teams",
  "employment_id": "EMP_NORTH",
  "occurred": {
    "start": "2016-03",
    "end": "2016-03",
    "inferred": false
  },
  "star": {
    "situation": "Service teams could not distinguish a quiet queue from a stalled consumer.",
    "task": "Expose queue age and ownership without replacing the messaging platform.",
    "action": "Designed a queue-age dashboard and paired with service owners to set alert thresholds.",
    "result": "Five services adopted the dashboard and ownership alerts."
  },
  "metrics": [],
  "skills": [
    "observability",
    "cross-team collaboration"
  ],
  "source_refs": [
    {
      "source_id": "SRC_SUBJECT",
      "excerpt": "2016-03: Service teams could not distinguish a quiet queue from a stalled consumer. Expose queue age and ownership without replacing the messaging platform. Designed a queue-age dashboard and paired with service owners to set alert thresholds. Five services adopted the dashboard and ownership alerts."
    }
  ],
  "evidence_status": "self_asserted",
  "external_safe": false,
  "outcome_type": "output",
  "corroborators": [],
  "constraints": []
}

{
  "employment_id": "EMP_CIVIC",
  "employer": "Fictional Civic Atlas",
  "employer_of_record": "Fictional Civic Atlas",
  "title": "Software Engineer",
  "start": "2010-09",
  "end": "2014-06",
  "parent_employment_id": null,
  "location": "London",
  "source_refs": [
    {
      "source_id": "SRC_SUBJECT",
      "excerpt": "Software Engineer at Fictional Civic Atlas, September 2010 to June 2014. Built data-import tools with a service-delivery team."
    }
  ],
  "external_safe": false,
  "evidence_status": "self_asserted",
  "corroborators": []
}

Context

Import failures were discovered after staff had started processing records.

Responsibility

Make failures visible before processing and leave a recovery path for operators.

Recorded dates

From

2012-04

To

2012-04

Dates are approximate

No

Recorded measures

Nothing recorded

Skills

• data engineering
• service operations

Outcome type

output

Corroborators

Nothing recorded

Constraints

Nothing recorded

{
  "id": "E_IMPORT_VALIDATION",
  "title": "Made data imports easier to recover",
  "employment_id": "EMP_CIVIC",
  "occurred": {
    "start": "2012-04",
    "end": "2012-04",
    "inferred": false
  },
  "star": {
    "situation": "Import failures were discovered after staff had started processing records.",
    "task": "Make failures visible before processing and leave a recovery path for operators.",
    "action": "Built validation checks and a rejected-record queue with the service-delivery team.",
    "result": "Operators used the checks across 18 recurring data feeds."
  },
  "metrics": [],
  "skills": [
    "data engineering",
    "service operations"
  ],
  "source_refs": [
    {
      "source_id": "SRC_SUBJECT",
      "excerpt": "2012-04: Import failures were discovered after staff had started processing records. Make failures visible before processing and leave a recovery path for operators. Built validation checks and a rejected-record queue with the service-delivery team. Operators used the checks across 18 recurring data feeds."
    }
  ],
  "evidence_status": "self_asserted",
  "external_safe": false,
  "outcome_type": "output",
  "corroborators": [],
  "constraints": []
}

Context

Routine recovery depended on an engineer remembering undocumented steps.

Responsibility

Help the operations team own routine recovery safely.

Recorded dates

From

2013-09

To

2013-09

Dates are approximate

No

Recorded measures

Nothing recorded

Skills

• knowledge transfer
• service operations

Outcome type

output

Corroborators

Nothing recorded

Constraints

Nothing recorded

{
  "id": "E_OPERATIONS_RUNBOOK",
  "title": "Handed routine recovery to operations",
  "employment_id": "EMP_CIVIC",
  "occurred": {
    "start": "2013-09",
    "end": "2013-09",
    "inferred": false
  },
  "star": {
    "situation": "Routine recovery depended on an engineer remembering undocumented steps.",
    "task": "Help the operations team own routine recovery safely.",
    "action": "Paired with operators to write recovery runbooks and rehearse failure cases.",
    "result": "Operations maintained the runbooks and performed routine recovery; no response-time baseline was recorded."
  },
  "metrics": [],
  "skills": [
    "knowledge transfer",
    "service operations"
  ],
  "source_refs": [
    {
      "source_id": "SRC_SUBJECT",
      "excerpt": "2013-09: Routine recovery depended on an engineer remembering undocumented steps. Help the operations team own routine recovery safely. Paired with operators to write recovery runbooks and rehearse failure cases. Operations maintained the runbooks and performed routine recovery; no response-time baseline was recorded."
    }
  ],
  "evidence_status": "self_asserted",
  "external_safe": false,
  "outcome_type": "output",
  "corroborators": [],
  "constraints": []
}

Built an engineering practice

Context

The group was trying a shared approach to design reviews.

Responsibility

Help engineers learn from each other.

Your contribution

Personally designed the peer review format, hired the engineers and coached every engineer.

What changed

The engineering group adopted peer design reviews.

Created a deployment rehearsal tool

Context

Product teams needed to test deployment steps before changing production.

Responsibility

Make deployment practice repeatable without taking delivery ownership from the teams.

Your contribution

Designed the rehearsal format and co-built its runner with engineers.

What changed

Two teams adopted rehearsals before deployment.

No excerpt attached to this item.

{
  "id": "S_DISTINCTIVE",
  "interpretation": "Helps teams adopt practical engineering approaches",
  "evidence_ids": [
    "E_STORY_1",
    "E_STORY_2"
  ],
  "evidence_fingerprints": {
    "E_STORY_1": "0c1e99191b3e2486f0bfd73f8efa84a6cf76c6ba950bbfa299a38243a42440ee",
    "E_STORY_2": "0fa9c90600a42c4319d754c023dc39d161a6f81740c78261afdb2bd8df916462"
  },
  "status": "proposed",
  "basis": "recurring_pattern",
  "limitations": [
    "Shared ownership matters; the coaching description needs correction."
  ],
  "timeframe": "Dates of the supporting achievements",
  "external_safe": false,
  "source_refs": [],
  "question_status": "open",
  "review_question": "Does this describe your contribution?"
}

Chose an adoption plan within team capacity

Context

Four product teams requested different platform improvements from the same small group.

Responsibility

Agree priorities and ownership within the available engineering capacity.

Your contribution

Worked with engineering managers and product leads to compare support burden and migration effort.

What changed

The group agreed a two-quarter platform adoption plan and named an owner for each migration; revenue impact was not measured.

Built an engineering practice

Context

The group was trying a shared approach to design reviews.

Responsibility

Help engineers learn from each other.

Your contribution

Personally designed the peer review format, hired the engineers and coached every engineer.

What changed

The engineering group adopted peer design reviews.

No excerpt attached to this item.

{
  "id": "S_ENTERPRISE",
  "interpretation": "Transforms engineering organizations at enterprise scale",
  "evidence_ids": [
    "E_PLATFORM_ADOPTION",
    "E_STORY_2"
  ],
  "evidence_fingerprints": {
    "E_PLATFORM_ADOPTION": "168d76dbad2bd8cad6e49c0c1e52ef2b45987c6080eef19d9f5392881993296a",
    "E_STORY_2": "0fa9c90600a42c4319d754c023dc39d161a6f81740c78261afdb2bd8df916462"
  },
  "status": "proposed",
  "basis": "recurring_pattern",
  "limitations": [
    "Deliberately overbroad proposed interpretation: the record covers a focused engineering group."
  ],
  "timeframe": "Dates of the supporting achievements",
  "external_safe": false,
  "source_refs": [],
  "question_status": "open",
  "review_question": "Does this describe your contribution?"
}

Chose an adoption plan within team capacity

Context

Four product teams requested different platform improvements from the same small group.

Responsibility

Agree priorities and ownership within the available engineering capacity.

Your contribution

Worked with engineering managers and product leads to compare support burden and migration effort.

What changed

The group agreed a two-quarter platform adoption plan and named an owner for each migration; revenue impact was not measured.

Agreed a gradual service separation

Context

Product and operations disagreed about replacing a shared service in one release.

Responsibility

Make the migration tradeoffs explicit and agree a sequence the teams could support.

Your contribution

Mapped failure boundaries with both groups and authored a staged separation proposal.

What changed

The teams chose a staged separation and retained a rollback path; product teams implemented the changes.

No excerpt attached to this item.

{
  "id": "S_TRANSLATION",
  "interpretation": "Makes technical tradeoffs understandable across teams",
  "evidence_ids": [
    "E_SERVICE_BOUNDARIES",
    "E_PLATFORM_ADOPTION"
  ],
  "evidence_fingerprints": {
    "E_SERVICE_BOUNDARIES": "d50b2452132d3abb16e56dfc1d1dbbf692efa73f09fcb4261eb8966d40c9fe2a",
    "E_PLATFORM_ADOPTION": "168d76dbad2bd8cad6e49c0c1e52ef2b45987c6080eef19d9f5392881993296a"
  },
  "status": "proposed",
  "basis": "recurring_pattern",
  "limitations": [
    "These examples show planning and agreement, not measured commercial outcomes."
  ],
  "timeframe": "Dates of the supporting achievements",
  "external_safe": false,
  "source_refs": [],
  "question_status": "open",
  "review_question": "Does this describe your contribution?"
}

{
  "education_id": "EDU_BSC",
  "institution": "Fictional Eastbank University",
  "qualification": "BSc",
  "field": "Computer Science",
  "start": "2006-09",
  "end": "2010-06",
  "grade": null,
  "evidence_status": "self_asserted",
  "external_safe": false,
  "source_refs": [
    {
      "source_id": "SRC_SUBJECT",
      "excerpt": "BSc in Computer Science, Fictional Eastbank University, September 2006 to June 2010. No grade supplied."
    }
  ]
}

No excerpt attached to this item.

"Jules Elm"

No excerpt attached to this item.

{
  "name": "Jules Elm",
  "location": "London"
}

No excerpt attached to this item.

"Entirely fictional career-review demonstration; never use as personal evidence."

No excerpt attached to this item.

{
  "source_id": "SRC_MANAGER",
  "source_type": "markdown",
  "path": "data/sources/manager-review-2025.md",
  "independent": true,
  "sha256": "452b7e943c97015f1d5c5d005b602ad95414d7428313233ef2e114fb52f09997",
  "character_count": 357
}

No excerpt attached to this item.

{
  "source_id": "SRC_TALK",
  "source_type": "markdown",
  "path": "data/sources/conference-programme.md",
  "independent": true,
  "sha256": "b70ba5456fff724e9fffc49df7a13bcf47ffe5e9270eb1ca0fb777b8ea9602ff",
  "character_count": 277
}

{
  "publication_id": "PUB_DEPLOYMENT_TALK",
  "title": "Practising deployments before production",
  "kind": "talk",
  "venue": "Community Systems Forum",
  "date": "2021-06",
  "role": "co_speaker",
  "collaborators": [
    "Mara Vale"
  ],
  "employment_id": "EMP_STAFF",
  "evidence_id": "E_TALK",
  "source_refs": [
    {
      "source_id": "SRC_TALK",
      "excerpt": "Community Systems Forum, June 2021: \"Practising deployments before production\". Co-presenters: Jules Elm and Mara Vale, Fictional Fieldwork Ltd. The programme establishes the shared talk title and speaker listing, not audience size or impact."
    }
  ],
  "evidence_status": "self_asserted",
  "external_safe": false,
  "url": null
}