# Issuer Directory Owner Manifest

**Decision ID:** OWNER-VEXLENS-001
**Status:** ASSIGNED
**Effective Date:** 2025-12-06

## Assignment

The **Issuer Directory Postgres backend** component is owned by the **VEX Lens Guild** for implementation purposes.

## Rationale

1. The Issuer Directory is a core VEX Lens subsystem defined in `src/VexLens/StellaOps.VexLens/Verification/`
2. VEX Lens Guild has domain expertise in VEX trust models and issuer verification
3. Postgres storage patterns are consistent with existing VEX Lens persistence layer
4. No external guild has claimed ownership despite repeated requests

## Scope

The VEX Lens Guild is responsible for:
- `IIssuerDirectory` implementation with Postgres backend
- Issuer CRUD operations and trust level management
- Integration with `SignatureVerifier` for issuer-based verification
- Schema migrations for issuer tables
- Observability (metrics, logging) for issuer operations

## Escalation Path

If blocked on infrastructure or cross-cutting concerns:
1. Platform DB Guild for Postgres operator issues
2. Security Guild for key management integration
3. Steering Committee for resource allocation

## Authority Granted

This manifest grants implementation authority to proceed with tasks blocked on staffing, specifically:

- SPRINT_3409: Issuer Directory Postgres staffing blocker
- VEX-30-003: Issuer Directory API implementation
- VEX-30-004: Policy integration for issuer trust

## Implementation Notes

- Use existing `InMemoryIssuerDirectory` as reference implementation
- Follow storage patterns from `src/VexLens/StellaOps.VexLens/Storage/`
- Apply RLS patterns from Findings Ledger for multi-tenancy