{"version":"2026-10-09","sha256":"7cf33804f4a218b26361c24ccad029befaec45b5e4d8bec98218aca5708b872c","scope":"Selected professional experience and applied AI implementations, with source context and scoped verification.","records":[{"key":"ai_case:bounded-control-plane","kind":"ai_case","architecture":["Authenticated role","Permitted tool contract","Bound confirmation","Controlled operation","Reviewable result"],"boundary":"Focused local policy and analytics tests with mocked provider dependencies.","category":"Governance","id":"bounded-control-plane","implementation":"I developed a control plane with role/tool policies, HMAC-bound confirmations, prompt and output filters, provider interfaces and template resolution. An analytics path fixes organisation scope before canonicalisation and cache-key generation, then calls a fixed aggregation interface rather than arbitrary generated SQL.","lesson":"The control must sit outside the prompt. Negative fixtures matter as much as the successful path.","problem":"An assistant that produces useful text should not automatically receive authority to change records or perform an external action.","stack":["TypeScript","Policy contracts","Signed confirmations","SQL aggregation"],"status":"Fresh local tests","summary":"I separate what a model recommends from what its role is allowed to do, using tool policies and confirmations tied to the actual action.","title":"A model can propose an action. Authority decides execution.","verification":"140 control-plane tests, 13 model-tier selection tests and 32 analytics-contract tests passed locally on 9 October 2026. Provider-registry and stream checks use mocked dependencies."},{"key":"ai_case:context-and-generation","kind":"ai_case","architecture":["Registered source material","Task-specific retrieval","Context sufficiency gate","Structured generation","Source-aware review"],"boundary":"Lexical retrieval, context sufficiency and structured-output validation are implemented in separate applications.","category":"Context engineering patterns","id":"context-and-generation","implementation":"I developed paths that assemble requirements, criteria, risks and selected prior material. Project memory and bounded chat history preserve continuity. Source-linked snippets support lexical retrieval. Sufficiency checks and output validation make missing context and malformed results explicit.","lesson":"Context engineering is a selection and responsibility problem. Keep the source of a fact visible after generation.","problem":"Operational archives contain inconsistent and irrelevant material. Passing everything into a prompt obscures requirements and supporting facts.","stack":["Python","TypeScript","Lexical retrieval","Structured validation"],"status":"Source inspected","summary":"I select the context for each task, check whether the sources are sufficient and require a structured output the next role can inspect.","title":"Give the model enough context, not the whole archive.","verification":"Context and generation code inspected across separate applications. The implementations preserve task requirements, source sufficiency and structured output contracts."},{"key":"ai_case:public-reference-shell","kind":"ai_case","architecture":["Local reference server","Defined action policies","Human decision boundary","Append-only records","Provider or explicit no-provider response"],"boundary":"A runnable local reference implementation using synthetic inputs and mocked providers, with owner-directed code review and published tests.","category":"Reproducible public work","id":"public-reference-shell","implementation":"I defined an architecture with replaceable model providers, local file memory, explicit human review for consequential actions and append-only audit records. The public shell implements selected mechanisms with synthetic demonstration data. Its implementation and assessment were produced with coding agents under my direction. Review exposed a malformed risk-input boundary. I directed a fail-closed fix and regression checks before publishing it.","lesson":"Make a useful claim small enough to reproduce. Simulations, inventory counts and model usage remain separate from observed operational value.","problem":"A description of safe agent behaviour is difficult to trust without runnable code, failure checks and explicit limits that another person can inspect.","references":[{"label":"Public reference shell and setup","url":"https://github.com/Haris88m/servari-open"},{"label":"Architecture, simulations and limits","url":"https://github.com/Haris88m/agentic-os-audit"}],"stack":["Python","Standard-library server","Deterministic tests","Mocked provider contracts"],"status":"Fresh local tests","summary":"I published a local-first reference shell so another person can inspect the action boundaries and see how provider selection behaves.","title":"A reference implementation you can inspect and run.","verification":"The public implementation passed 384 local tests on 9 October 2026, including 224 added numeric-domain and CLI regressions, plus eight verifier checks. Published CI also completed the Python suite, verifier and UI build. The tests use synthetic fixtures and mocked providers."},{"key":"ai_case:receipt-bound-workflows","kind":"ai_case","architecture":["Validated preparation","Authorised action","Case-bound receipt","Integrity verification","Recorded completion"],"boundary":"Local workflow tests cover case identity, file integrity and state transitions using temporary fixtures.","category":"Workflow integrity","id":"receipt-bound-workflows","implementation":"I developed a persistent workflow requiring a validated receipt associated with the same case. It checks the stored SHA-256 hash before recording completion and rejects missing, unrelated or changed receipts. Source-linked claim checks remain a separate layer so evidence acceptance is not confused with execution success.","lesson":"Define completion through evidence another person can inspect, not the confidence of the last message.","problem":"A workflow can look finished after an attempted action without valid confirmation. Later decisions may then rely on a false completion record.","stack":["Python","SQLite","SHA-256","State transitions"],"status":"Fresh local tests","summary":"I require a matching receipt and file-integrity check before the workflow records an action as completed.","title":"Attempted is not completed.","verification":"18 application-engine tests passed locally on 9 October 2026 using in-memory databases and temporary receipts. Those tests submitted no real applications."},{"key":"ai_case:reliable-ingestion","kind":"ai_case","architecture":["Source adapters","Bounded attempts","Retrieval provenance","Canonical matching","Health records and updates"],"boundary":"Source-isolated ingestion with deadlines, provenance and health records. Cancellation and identifier fallback are the next reliability checks.","category":"Reliability","id":"reliable-ingestion","implementation":"I directed a multi-source ingestion path with independent settled outcomes, per-source 30-second deadlines, isolated diagnostics and source-health records. Adapter logic handles an upstream API version and records parser and retrieval provenance. Canonical external identifiers support matching and update/backfill behaviour.","lesson":"Diagnose each source separately. Keep incomplete records and upstream failures visible rather than reporting a misleading clean aggregate.","problem":"Upstream sources change formats, fail independently and return incomplete records. A slow source can stall discovery and inconsistent identifiers can duplicate records.","stack":["TypeScript","Edge functions","API adapters","Data normalisation"],"status":"Source inspected","summary":"Independent source processing, deadline handling, stable identifiers and health records support multi-source ingestion.","title":"A broken source should not block every other source.","verification":"Current source inspected on 9 October 2026, including per-source deadlines, parser provenance, source health and canonical matching."},{"key":"ai_case:specialist-orchestration","kind":"ai_case","architecture":["Shared task context","Three bounded branches","Settled results and failures","Dependent synthesis","Complete or partial result"],"boundary":"Three specialist analyses and a separate synthesis stage, implemented with provider abstraction and explicit partial results.","category":"Orchestration","id":"specialist-orchestration","implementation":"I directed an explicit fan-out/fan-in workflow. Three specialists receive shared context and return separate findings. A dependent synthesis combines available results. Fulfilled and rejected branches are handled independently and a partial run remains identifiable.","lesson":"Parallelism only helps if the downstream step knows what it can rely on. A partial result needs a different acceptance decision.","problem":"A complex decision needs several perspectives. One long response makes it difficult to see which analysis completed and which input failed.","stack":["TypeScript","Asynchronous orchestration","Provider abstraction"],"status":"Source inspected","summary":"I built a workflow in which three specialist analyses share the same context and feed a separate synthesis stage. If a branch is incomplete, the next role sees the gap.","title":"Separate the analysis. Keep one accountable decision.","verification":"Orchestration source inspected on 9 October 2026. The implementation handles fulfilled and rejected branches independently before synthesis."},{"key":"career_case:country-office-operations","kind":"career_case","accent":"green","boundary":"Delegated supplier maintenance, voucher creation, ICT and asset functions, alongside procurement case management, HR coordination and financial follow-through.","category":"Operations","context":"CORE operations and concurrent programme portfolios required prioritisation, operational continuity, financial discrepancy resolution and clear accountability across offices.","contribution":["I carried out procurement focal-point and case-manager work, connecting programme requirements, suppliers, documentation and the approval process.","I held four signed delegations covering Regional Office Supplier Maintenance, Regional Office Voucher Creation, North Macedonia ICT Focal Point and North Macedonia Asset Focal Point.","I processed PO and non-PO vouchers, resolved matching exceptions, routed approvals and followed payments through to completion.","I reconciled outstanding and expected invoices against purchase-order balances and explained amendment requirements directly to headquarters procurement.","I developed and tracked operational budgets, contributed to revisions and forecasts, and worked with office leadership on risks and delivery priorities. I also represented North Macedonia in regional operational meetings.","I coordinated with regional and other country offices and UNDP counterparts, handled HR focal-point responsibilities including recruitment coordination and everyday HR questions, and maintained shared operational knowledge. I completed the 2021 greenhouse-gas inventory exercise in 2022."],"evidence":"Signed delegations, invoice reconciliation, professional correspondence, service evaluations and my confirmed responsibilities.","id":"country-office-operations","inputs":["Programme requirements, budgets and forecasts across concurrent portfolios","Purchase orders, invoices, supplier records and pending payments","Regional guidance, system changes and managerial decisions"],"outputs":["Reconciled invoices, payment follow-through and clear amendment requests","Supplier and financial records maintained through delegated system roles","Budget follow-through, management visibility and continuity across programmes","Practical support for colleagues and suppliers during systems change"],"reuse":"Cross-functional operations, accountable financial workflows, supplier management and distributed programme delivery.","roles":["operations","programme-delivery"],"status":"Professional experience","summary":"At UN Women, I connected programme delivery with budgets, procurement, financial processing and country-office operations, working directly with office leadership, regional colleagues and headquarters.","title":"Country-office delivery with regional responsibility","tools":["Quantum","Atlas","UNall","SharePoint","Microsoft Teams","Email"]},{"key":"career_case:enterprise-workflow-adoption","kind":"career_case","accent":"amber","boundary":"Functional implementation, supplier enablement and practical support through system change.","category":"Digital adoption","context":"A new platform changes more than a screen. Accounts, data requirements, responsibilities and the sequence of approvals all have to work for the people using it.","contribution":["I helped suppliers and colleagues understand what new workflows required and how to use them.","I translated guidance into usable next steps and followed up on registration and process issues.","I shared what I learned during implementation and worked with the responsible teams to resolve outstanding errors."],"evidence":"Systems-adoption correspondence, procedural guidance and supplier-workflow records.","id":"enterprise-workflow-adoption","inputs":["New platform guidance and process requirements","Supplier registration and workflow questions","Errors and practical issues reported by users"],"outputs":["Practical guidance for colleagues and suppliers","Follow-through on onboarding and workflow issues","Continuity while new procedures were adopted"],"reuse":"Implementation coordination, customer onboarding, workflow change and digital operations.","roles":["digital-adoption","operations","ai-operations"],"status":"Professional experience","summary":"I helped colleagues and suppliers adopt Quantum and UNall by turning new requirements into practical steps and resolving day-to-day workflow problems.","title":"Turning system change into daily practice","tools":["Quantum","UNall","Email","Microsoft Teams"]},{"key":"career_case:evidence-workflow","kind":"career_case","accent":"violet","boundary":"A working local system with review gates, recorded outcomes and continuing development.","category":"AI & systems","context":"Documents, correspondence and earlier applications contained different versions of the same experience. Reliable output needed a structure for evidence, uncertainty and review.","contribution":["I defined how source material, supported statements and final documents relate to one another.","I directed specialist agents to retrieve, challenge, implement and validate defined pieces of work.","I set review points and required confirmation of outcomes before treating an action as complete."],"evidence":"Working implementation, structured records, automated checks and recorded outcomes.","id":"evidence-workflow","inputs":["Professional documents and approved correspondence","An evidence hierarchy and wording constraints","A specific role or research objective"],"outputs":["Reusable statements linked to supporting evidence","Role-specific document packages and review records","An operational history of actions, blockers and confirmed outcomes"],"reuse":"Document-heavy research, professional knowledge management and controlled operational workflows.","roles":["ai-operations","digital-adoption","operations"],"status":"Implemented local system","summary":"I built an AI-assisted local system that turns a professional archive into traceable statements, tailored documents and a record of outcomes.","title":"From a fragmented archive to usable evidence","tools":["Multi-model workflows","Python","SQLite","Automated checks"]},{"key":"career_case:institutional-project-delivery","kind":"career_case","accent":"blue","boundary":"Expert mobilisation, financial control and institutional coordination within each project's governance.","category":"Programme delivery","context":"NSF Euro Consultants focused on consumer-protection policy, Evoluxer on market-surveillance legal harmonisation, and Pohl Consulting and Associates on bankruptcy and liquidation reform.","contribution":["At NSF, I developed and tracked project budgets, checked invoices against budget forecasts, prepared monthly cash requirements and supported cash-flow projections. I also worked on activity costing and budget reallocations as the consumer-policy plan developed.","At Evoluxer, I planned expert inputs, maintained working-day controls and developed a resource-allocation proposal covering 11 EU product-safety directives, linking specialist work with institutional requirements and delivery deadlines.","At Pohl, I prepared monthly expense reports and cash requirements, tracked office costs and incidentals, and coordinated expert activity, training and study visits. I later supported final reporting and defined financial-closeout work."],"evidence":"Signed project duties, employer references, budget and expense workbooks, expert-day plans and implementation correspondence.","id":"institutional-project-delivery","inputs":["Project work plans, budgets and expert assignments","Institutional meeting and training requirements","Deliverables, reporting schedules and implementation records"],"outputs":["Costed activities, cash requirements and budget revisions","Expert-day plans, expense controls and reporting inputs","Coordinated institutional activity, training and deliverables"],"reuse":"Programme coordination, PMO, implementation and multi-stakeholder project environments.","roles":["programme-delivery","operations"],"status":"Professional experience","summary":"I managed day-to-day delivery across three EU-funded reform projects, connecting budgets, expert inputs, public institutions and reporting deadlines.","title":"Making institutional reform deliverable","tools":["Work plans and expert-day controls","Budget and cash-flow workbooks","Microsoft Excel","Institutional correspondence"]},{"key":"career_case:product-prototyping","kind":"career_case","accent":"amber","boundary":"Working prototypes with implemented interfaces, application logic and recorded technical validation.","category":"AI & systems","context":"A concept needed to become something that could be used and tested. That required explicit behaviour, clear acceptance criteria and repeated review of what was actually built.","contribution":["I shaped the product brief and directed implementation with coding agents.","I reviewed interfaces, data flows and behaviour against the intended use.","I checked tests, types and the production build before accepting the prototype checkpoint."],"evidence":"Source implementation and the recorded prototype validation checkpoint.","id":"product-prototyping","inputs":["User needs and product requirements","Interface and workflow specifications","Acceptance criteria and implementation constraints"],"outputs":["A substantial working digital prototype","Implemented interfaces and application logic","Recorded technical validation at the accepted checkpoint"],"reuse":"AI-assisted implementation, product operations and translating a brief into testable software.","roles":["ai-operations","digital-adoption","programme-delivery"],"status":"Working prototype","summary":"I use AI-assisted engineering to take product requirements through interface design, implementation and technical validation.","title":"Taking a product brief into working software","tools":["Coding agents","Version control","Automated tests","Web application tooling"]},{"key":"career_case:senior-mission-coordination","kind":"career_case","accent":"blue","boundary":"Country-office team preparation and assigned operational workstreams supporting institutional engagements.","category":"Programme delivery","context":"The mission connected country-programme priorities with public institutions, international partners, civil society and field activity over a tightly sequenced agenda.","contribution":["I worked with the country-office team on preparation and coordinated my assigned implementation requirements.","I aligned event services, suppliers and movement arrangements with the wider mission sequence.","I kept dependencies visible and brought decisions to the responsible colleagues in time for delivery."],"evidence":"Mission planning material, procurement records and implementation correspondence.","id":"senior-mission-coordination","inputs":["Mission schedule and country-programme priorities","Institutional, field and event requirements","Supplier options and changing practical dependencies"],"outputs":["Coordinated assigned mission and field requirements","Supplier recommendations and delivery follow-through","Operational preparation aligned with institutional engagements"],"reuse":"Senior stakeholder coordination, programme missions, events and complex delivery.","roles":["programme-delivery","operations"],"status":"Professional experience","summary":"I contributed to country-office preparation and coordinated assigned delivery work for the October 2024 visit by senior global and regional UN Women leadership.","title":"From a senior mission plan to delivery","tools":["Mission schedules","Supplier records","Programme coordination","Office tools"]},{"key":"learning_path:context","kind":"learning_path","acceptance":"A versioned report with comparable inputs, human-reviewed labels, failures and clear limits.","built":"Task-specific context, lexical retrieval, sufficiency gates and structured generation.","id":"context","next":"Create a fixed evaluation set for source coverage, unsupported claims and abstention. Compare prompt versions on the same cases.","title":"Context to a reviewable output"},{"key":"learning_path:handoff","kind":"learning_path","acceptance":"A user can operate and stop the workflow without its original author. Reuse and support effort are documented.","built":"Human-directed specialist work, policy boundaries and practical system adoption in international operations.","id":"handoff","next":"Package a synthetic example with dependencies, owner, fallback, test fixtures and handoff instructions. Trial reuse in a second setting.","title":"From personal expertise to reusable practice"},{"key":"learning_path:measurement","kind":"learning_path","acceptance":"Comparable accepted cases and a measured outcome. Capacity released and cash saved are reported separately.","built":"Operational reconciliation, source-linked records and accountable completion states.","id":"measurement","next":"Pilot a workflow with an independent user. Record baseline effort, assisted review and correction time, quality and direct running cost.","title":"From a working tool to evidence of value"},{"key":"learning_path:reliability","kind":"learning_path","acceptance":"Reproducible failure fixtures, an operator runbook and evidence that a second person can recover the workflow.","built":"Provider selection, failure-isolated ingestion and deterministic policy and workflow tests.","id":"reliability","next":"Add fault injection for stalled sources, retries, duplicates and confirmation replay. Establish bounded retry and recovery behaviour.","title":"From local checks to operational reliability"},{"key":"metric:analytics-contract","kind":"metric","checked_on":"2026-10-09","id":"analytics-contract","label":"Analytics-contract tests","limitations":"Focused contracts, not arbitrary query safety or production certification.","scope":"Fixed-scope aggregation and canonical cache contracts","value":32,"verification":"Passed locally"},{"key":"metric:chat-contract","kind":"metric","checked_on":"2026-10-09","id":"chat-contract","label":"Chat checks","limitations":"Not a factual-accuracy benchmark or a complete end-to-end application suite.","scope":"Focused context and chat behaviour checks","value":6,"verification":"Passed locally"},{"key":"metric:control-plane","kind":"metric","checked_on":"2026-10-09","id":"control-plane","label":"Control-plane tests","limitations":"Not the full application suite or a live security certification.","scope":"Focused local policy and confirmation suite","value":140,"verification":"Passed locally"},{"key":"metric:mocked-dispatch","kind":"metric","checked_on":"2026-10-09","id":"mocked-dispatch","label":"Mocked dispatch checks","limitations":"Mocked dependencies only; no live provider execution.","scope":"Provider registry and stream contracts","value":3,"verification":"Passed locally"},{"key":"metric:model-tier","kind":"metric","checked_on":"2026-10-09","id":"model-tier","label":"Model-tier tests","limitations":"Provider dependencies are mocked; no quality or cost benchmark.","scope":"Focused model-selection contract suite","value":13,"verification":"Passed locally"},{"key":"metric:public-shell","kind":"metric","checked_on":"2026-10-09","id":"public-shell","label":"Historical public reference-shell tests","limitations":"Mostly mocked providers. This historical commit had numeric input-validation limitations, corrected in a later commit. Passing tests are not security certification.","scope":"Historical pristine commit fdc9f5924d3e9a30d0780b3d830c33b0b6f814f1","value":160,"verification":"Passed locally before the numeric-boundary hardening"},{"key":"metric:public-shell-current","kind":"metric","checked_on":"2026-10-09","id":"public-shell-current","label":"Hardened public reference-shell tests","limitations":"Mostly mocked providers; not a live security certification, full deployment audit or measured business outcome. This is a later run of the same suite, not an additional independent benchmark.","scope":"Public commit 8c39bbff57fb72e01990dc5ecd162fb8a1745378, including 224 added numeric-boundary and command-line regression cases","value":384,"verification":"Passed locally after the numeric-boundary hardening"},{"key":"metric:public-verifier","kind":"metric","checked_on":"2026-10-09","id":"public-verifier","label":"Public verifier checks","limitations":"Not internet-facing security certification, organisational adoption or measured ROI.","scope":"Separate verifier against the public reference shell","value":8,"verification":"Passed locally, including an isolated local HTTP smoke check"},{"key":"metric:receipt-workflow","kind":"metric","checked_on":"2026-10-09","id":"receipt-workflow","label":"Receipt-workflow tests","limitations":"In-memory databases and temporary receipts; no real application was submitted by these tests.","scope":"Application-engine integrity transitions","value":18,"verification":"Passed locally"}],"total":29,"limit":25}