Regulatory Architecture

Strategy: registration as moat

Dark Matter's regulatory strategy leads with registration, not exemption arguments. Registration removes ambiguity, signals institutional seriousness, and creates barriers to entry. The architecture enforces these boundaries in code regardless of registration status.

Broker-dealer subsidiary

DMTR intends to register a subsidiary as a limited-purpose broker-dealer under the "rails" model, analogous to DTCC/DTC/NSCC. The RBAC and visibility tier boundaries enforce this architecturally — IOI creation requires the broker_dealer role, and cross-platform position discovery is gated by visibility tier. The BD subsidiary is also designated as the operator of a Qualified Matching Service (QMS) under Treas. Reg. § 1.7704-1(g), raising the PTP safe harbor from 2% to 10% of outstanding interests annually.

Estimated costs: FINRA new member application $75-150K in legal fees + $50-75K in FINRA fees, 6-12 month timeline. Annual compliance: $300-500K (designated compliance officer, FOCUS reports, customer protection rule compliance, net capital). Net capital requirement: $250K minimum for a non-clearing BD.

Platform is not an ATS

Under Exchange Act Rule 3b-16(a), an ATS requires bringing together "orders" and using "non-discretionary methods" for order interaction. The platform satisfies neither: no order book, no automated matching, no anonymous counterparties. Every transfer requires discretionary human action (Managing Member consent, ROFR exercise, potentially counsel review). The BD subsidiary facilitates each transfer as broker; the platform is recordkeeping and compliance infrastructure, not an execution venue. Five structural safeguards: no anonymous counterparties, no automated price formation, no continuous market, all transfers require BD intermediation, pre-existing substantive relationship required.

Transfer agent registration

DMTR is filing for SEC transfer agent registration (Form TA-1, 45-day process, under $10K). The operating agreement language structures the Managing Member as the contractual transfer agent using DMTR as its recordkeeping platform — this is belt-and-suspenders alongside registration.

Secondary transfer exemption: Section 4(a)(7)

All secondary transfers of DOIV membership interests rely on Section 4(a)(7) of the Securities Act (FAST Act, December 2015) as the primary resale exemption. 4(a)(7) provides a statutory safe harbor for private resales between accredited investors with NSMIA preemption of state blue sky registration. The Rights Engine verifies all 4(a)(7) requirements programmatically: purchaser accreditation, no general solicitation, non-issuer seller, non-dealer seller, 90-day outstanding period, no bad actors, and financial information availability per Rule 15c2-11(a)(5). Section 4(a)(1-1/2) is the fallback for transfers within the first 90 days. See docs/strategy/doiv-transfer-structure-memo.md for the full legal analysis.

Compliance-as-a-service

Registered BD and TA infrastructure can be offered to other secondary marketplaces (Forge, CAIS, InvestX). Any platform transacting in LLC interests needs a transfer agent and often uses a broker-dealer. Positions using DMTR's TA/BD services are one step from being fully DMTR-encoded. This turns the regulatory cost center into a revenue line and extends the network effect.

Architectural enforcement

RBAC roles and permissions

DMTR enforces regulatory boundaries through role-based access control. Key roles:

• gp: Full access to fund operations, consent, settlement
• lp: Read own positions, transfers, and documents
• buyer: Search positions (filtered by IssuerRelationship), create transfers
• broker_dealer: IOI creation, cross-platform position discovery at accredited_only and qualified_purchaser visibility tiers
• lender: Read collateral pools, verify coverage, view pledged positions
• admin: Platform-level administration

IOI creation requires the broker_dealer role. Buyers retain position search but results are filtered by the visibility tier and issuer relationship system — buyers can only discover positions where they have a documented pre-existing relationship. Broker-dealers get broader discovery.

Visibility tiers (Issuer-Level Visibility Controls)

Every position carries an optional visibility_tier:

• private (506(b)): Only visible to participants with a documented IssuerRelationship. Prevents general solicitation — blowing an issuer's Reg D exemption is irreversible.
• accredited_only (506(c)): Visible to verified accredited investors and broker-dealers.
• qualified_purchaser (3(c)(7)): Visible to qualified purchasers and broker-dealers.
• unrestricted: Standard role-based filtering.

The filterPositions() function in the data isolation layer enforces these tiers at the query level. A 506(b) position structurally cannot appear in search results for participants without a documented pre-existing relationship.

counsel_review verdict type

The Rights Engine returns counsel_review (not pass or fail) for checks that require human legal judgment:

• ERISA benefit plan investor threshold analysis
• Qualified purchaser determination under Section 3(c)(7)
• Bad actor analysis under Rule 506(d)
• PTP safe harbor analysis under IRC 7704
• Complex jurisdictional/sanctions analysis beyond ITAR/CFIUS boolean checks
• ITAR periodic re-verification (stale or missing U.S. Person verification)

When requires_counsel_review is true, the transfer cannot settle until a document.signed event with document_type: "counsel_opinion" is recorded. This creates a hard gate for non-deterministic compliance checks.

ITAR periodic re-verification

Positions flagged as itar_sensitive require periodic re-verification of the holder's U.S. Person status. The ComplianceState schema tracks itar_last_verified (ISO date of last verification) and itar_reverification_interval_days (default: 365). The itar_reverification Rights Engine check returns counsel_review when verification is missing or stale, and conditional when verification is approaching expiry (90% of interval). This mirrors the bank sanctions re-screening pattern and mitigates ITAR criminal exposure (22 CFR §§ 120-130: up to 20 years imprisonment and $1M per violation).

Settlement and escrow

DMTR coordinates settlement but never holds or transmits funds. All cash-settled transfers require a third-party escrow agent (North Capital, Prime Trust, or a bank). This is enforced by the escrow_required Rights Engine check, which returns fail for any cash-settled transfer lacking a recognized third-party escrow provider.

Non-cash transfers and internal restructurings (e.g., contribution of assets into a DOIV) may use the manual escrow provider.

This policy prevents money transmitter registration requirements at the state level (50 state applications, $1-2M in surety bonds, 12-18 months).

Fund-level compliance

FundComplianceState

Each fund vehicle tracked in DMTR carries a FundComplianceState that enables three fund-level compliance checks:

ERISA tracking: Monitors benefit plan investor percentage against the 25% threshold (DOL Reg. § 2510.3-101). Transfers that would breach the threshold require counsel review.

Investment Company Act (three-tier analysis): The default operational posture is Section 3(c)(7) — unlimited holders, all must be qualified purchasers. Section 3(b)(2) exclusion is being pursued as an exemptive order (the DOIV is a position, not a portfolio — a single-asset wrapper with no investment discretion). Section 3(c)(1) with feeder is the tertiary path for non-QP accredited investors. The Rights Engine verifies QP status for 3(c)(7) vehicles and tracks the 100-owner cap for any 3(c)(1) vehicles.

PTP safe harbor (IRC 7704): The platform supports two settlement tracks. QMS track (primary): Transfers through the BD subsidiary operating as a Qualified Matching Service under Treas. Reg. § 1.7704-1(g) are disregarded in the PTP analysis — annual budget of 10% of outstanding interests, with a 45-day settlement floor. De minimis track (fallback): Treas. Reg. § 1.7704-1(h) limits transfers to 2% per year, with no settlement speed constraint. Certain transfer types are exempt from both counts: transfers by reason of death, between family members (IRC § 267(c)(4)), or block transfers of 50%+ of interests (§ 1.7704-1(e)). The Rights Engine tracks YTD percentages against the applicable limit and flags transfers approaching 80% of budget.

Transfer agent structure

The OA template supports two TA designation models, controlled by the ta_model field on OperatingAgreementVars. Outside counsel will advise on which path is appropriate.

Variant A: Managing Member as transfer agent

The operating agreement designates the Managing Member as the transfer agent and registrar, using DMTR as its recordkeeping system. The Managing Member retains independent judgment and override authority on all transfer determinations. The Managing Member may rely on the Rights Engine as a compliance tool but is not bound by its output. This is the belt-and-suspenders model: the Managing Member is the statutory TA, and DMTR files for its own TA registration independently.

Variant B: Platform as transfer agent

The operating agreement designates Dark Matter Technology, Inc. (or its TA subsidiary) as the transfer agent and registrar. The Managing Member retains override authority on all transfer determinations but does not itself serve as the TA. This model avoids imposing registration attributes on the fund manager — particularly relevant when the DMTR operator and fund manager share common control.

Shared provisions (both variants)

The Managing Member is required to independently review: (i) all proposed transfers above a specified value threshold, (ii) all transfers involving a new beneficial owner not previously approved, and (iii) a random sample of routine transfers per calendar quarter. The event log distinguishes between managing_member.approved_via_rights_engine (automated) and managing_member.approved_independently (manual review).

The Managing Member may rely on Rights Engine evaluations as commercially reasonable evidence of compliance, provided the underlying Position Object data is current and complete and the Managing Member has no actual knowledge of facts that would render the evaluation inaccurate. The Managing Member may waive the requirement for an opinion of counsel when the Rights Engine determines all mechanical conditions are satisfied — but may not waive counsel opinions when any check has returned a counsel_review determination.

UCC Article 8 and collateral perfection

The DOIV operating agreement opts membership interests into UCC Article 8 as uncertificated securities. Control perfection is achieved through the Managing Member (as the entity maintaining the register) agreeing to comply with instructions from the secured party pursuant to UCC Section 8-106(c)(2). DMTR is the recordkeeping system the Managing Member uses — not a securities intermediary under UCC 8-102(a)(14). This avoids the intermediary duties (8-504 through 8-509) while preserving control-based perfection with priority over filing under UCC Section 9-328.

Carry clawback

The operating agreement includes a standard clawback provision (Section 4.3): upon dissolution, if aggregate carry distributions exceed what would have been distributable in a single liquidating distribution, the excess is returned by carry recipients. This provision is interpreted consistently with the Fund LPA.

Data segregation

DMTR maintains logical data segregation between investment vehicles. Position data, participant identity, and transfer activity for each vehicle are accessible only to authorized participants and the Managing Member. No affiliate of DMTR has access to position data of vehicles managed by unaffiliated general partners, except in aggregate anonymized form for operational purposes.

Insurance and risk

Platform operators should maintain Errors & Omissions (E&O) insurance covering Rights Engine determinations. The DMTR Terms of Service include a disclaimer: the Rights Engine provides automated compliance checks based on encoded position data and does not constitute legal advice.

Related

• Rights Engine — Enforces regulatory rules
• Identity Graph — Participant identity data
• Brownfield Onboarding — Fidelity spectrum and wrapping
• Lookthrough Decomposition — Series and participation interest structures