Portfolio and property context
Navigate authorized portfolio and property hierarchy, unit-level records and a shared asset directory.
An evidence-governed asset decision-intelligence product for multifamily ownership teams. AME connects operating and physical-asset records across ownership, shows where the business plan and operating reality diverge, identifies what is documented or still missing, and brings decisions, authorized actions and eventual outcomes into one asset context.
An asset’s condition is distributed across acquisition assumptions, operations, leasing, capital expenditures, physical components, market evidence and ownership decisions. A variance may be visible while its explanation remains unsupported.
AME keeps property identity, source evidence, lifecycle, plan-versus-actual observations, uncertainty, human authorization, execution and outcomes connected without confusing them. Deterministic code retains arithmetic authority; model assistance cannot invent a cost or approve an unsupported fact.
AME V0.3 introduces a connected account experience organized around the asset rather than disconnected reports. Individual account journeys remain under founder acceptance and subsequent integration testing.
Navigate authorized portfolio and property hierarchy, unit-level records and a shared asset directory.
Distinguish equipment slots from installed items; preserve known presence, known absence, unknown status, condition, installation and replacement history as separate facts.
Connect documented costs, qualified quotes, expenses and rent or revenue history to the relevant asset and period. Unsupported estimates are not treated as financial fact.
Receive sources, preserve provenance, surface conflicting records and identify exactly what information is still required.
Bring current facts, material variances, unresolved information and human-authorized decision states into one operating view. Keep proposed actions separate from execution and outcome.
Generate evidence-bounded reports and explore admitted information through an advisory interface, subject to source availability, access permissions and tested behavior.
These are different validation classes. No single coverage figure, browser test or cloud deployment establishes a completed external pilot.
The earlier RC2 milestone reached 100% statement and branch coverage across 1,825 statements and 500 branches. This validates that tested boundary, not predictive superiority.
PostgreSQL tenant isolation and authenticated workflows have been exercised with RLS and browser tests, including Firefox and WebKit. Their scope remains the tested cases.
Container builds, non-root runtime checks, ZAP/Trivy security scans, SBOM generation and CI security gates have been exercised under separate receipts.
Container images have been published to Azure Container Registry at immutable digests, with artifact readback and signing/verification work. Artifact identity is not runtime correctness.
The private V0.3 release includes an Azure API/database and Cloudflare interface, with a healthy API revision and completed database migration in the release evidence. Later hosted development is distinct from that live version.
September 21 PR #12 records 313 passed, one skipped, 84 subtests, eight live RLS tests and 28 Playwright tests. The PR remains an undelivered development candidate rather than the live release.
AME is a private product under continued founder acceptance, integration and release hardening. Current evidence does not establish generally available SaaS, a completed external design-partner pilot, measured causal NOI improvement, a production SLA, certification, autonomous procurement or legal authority.
Physical condition, costs, source corrections and lifecycle predictions remain subject to their individual evidence and authorization. A passing test, signed image or cloud deployment does not independently authorize a broader business claim.
AME is being developed for ownership teams and qualified operating, asset-management, diligence and advisory partners. A scoped evaluation starts with a real property/portfolio question, available sources, a decision and explicit success criteria.
Pilot data access, supported integrations, success criteria and commercial terms are established individually. Unsupported modules and unreleased research are not represented as available functionality.