ARCHITECTURE DESIGN · APPLIED TO MICHELLE’S SITE

One purpose.
A traceable path.

Your sketch becomes a working connection between the data dictionary, API capabilities, business objectives, function proposals and validation evidence.

This copied app has a deterministic local guide. The registry documents application functions; it does not connect an LLM or change Michelle’s separate Maya service.

From a function request
to a verified result.

The current website guide uses its own deterministic /api/guide path to return navigation actions. The function API below is a separate, validated execution boundary; a future model would need an explicit integration.

01

Request

A caller supplies a function name, arguments and optional context for a stated business objective. No LLM caller is connected here.

02

Registry

Choose an implemented function with a known input/output contract and permission boundary.

03

Validation

Check arguments, allowed actions and required data connections before execution.

04

Source

Read curated data or an authorized property provider. Unavailable data stays unavailable.

05

Result

Return a source-backed answer, a bounded navigation action, a reviewable draft or an explicit disabled result.

06

Evidence

Record the outcome, timestamp and contract fingerprint, then review readiness separately from test success.

The three inputs
Codex works from.

Data dictionary

Defines business identity, community fields, article content, source authority, image context and email-off policy.

lib/site-data.ts

API capabilities

Lists actual function names, schemas, endpoint, dependencies, expected results and permissions. Proposals stay outside the execution allowlist.

lib/functions/registry.ts

Business objectives

Local discovery, verified home information, visitor-controlled contact, useful content and clear capabilities. No invented ranking, lead or revenue promise.

businessObjectives[]

Where the
data lives.

StoreCurrent useBoundary
TypeScript + JSON source filesBusiness facts, communities, Journal, function definitions and proposals.Published with a versioned deployment. No visitor write interface.
Contract source manifestContent hashes of the function implementation and its data/validation dependencies.Build/test hooks regenerate it. Changed contracts invalidate earlier evidence.
Verification JSONDated test outcomes, request guard results, response hashes and the tested contract fingerprint.Synthetic, nonpersonal checks. Public read-back does not run functions or send messages.
Browser stateCurrent chapter, selected community, search preferences and an optional inquiry draft.Navigation context is not identity or verified listing data.
External property providerFuture authorized public listing reads.Not connected in this app. No provider credentials are copied from Michelle’s main site.

A new database is not needed for this read-only registry. If editable approvals, authenticated editorial drafts or durable visitor records are added later, they need a separate storage and access design. This release does not create those capabilities.

Permissions
stay explicit.

A repeatable
validation loop.

  1. Document the function against a business objective and the data dictionary.
  2. Define input, output, permission and unavailable-result contracts.
  3. Run positive, negative and no-delivery tests.
  4. Publish, then verify the actual API response with synthetic inputs.
  5. Save dated evidence against the contract fingerprint and publish the report.
  6. After a source or contract change, treat previous evidence as stale until rechecked.

The input schemas use the JSON Schema object vocabulary. The app enforces the declared input subset and keeps domain conditions in the existing validators.