brotaparser 0.1.0

A Rust parser and compiler for declarative frontend architecture contracts.
Documentation
# `angular@0.1` Specification

## Required declaration

```brota
contract admin-panel {
  language "0.1"
  profile angular version "0.1"
  root "src"
}
```

The profile supports named feature areas:

```brota
contract admin-panel {
  language "0.1"
  profile angular version "0.1"
  root "src"
  area movie-reel
  area show-times
  area reserve-tickets
}
```

## Blueprint layout

The machine-readable `angular@0.1` Blueprint freezes the initial generated
layout. Consumers may instantiate the profile with their own named feature
areas; the built-in resolver uses these deterministic example areas:

```text
src/app/
  app.config.ts
  app.routes.ts
  app.ts
  core/
  shared/
  catalog/
  checkout/
  users/
```

The shell owns bootstrap and routing. `core` contains application-wide support
concerns and `shared` contains reusable UI/domain-neutral pieces. Each named
feature area co-locates its components, services, routes, tests, and public API.
The profile does not create `domain`, `application`, `infrastructure`, or
`presentation` layers, and it does not create global `components` or `services`
directories.

The derived diagnostic contract expresses those negative layout constraints with
forbidden path declarations:

```brota
forbid path "src/app/domain/**"
forbid path "src/app/services/**"
```

Comments are supported as non-semantic source trivia:

```brota
// Explain a decision for reviewers.
/* Explain a longer constraint. */
```

Line comments use `//` and block comments use `/* ... */`. Comments do not
change the normalized contract or its serialized representation. Comment
markers inside quoted strings remain string content.

Declared relationships are preserved in the normalized contract, but the
baseline profile does not invent dependency direction that Angular's style
guide does not prescribe.

## Deterministic rules

- The profile identifier and version MUST be supported explicitly.
- The source root MUST be present and non-empty.
- Area identifiers MUST be unique.
- Dependency endpoints MUST reference declared areas.
- Dependency rules MAY be `allow`, `forbid`, or `require` rules.
- Path rules MAY assign workspace-relative patterns to areas.
- Required artifacts MAY declare files, directories, public APIs, exports,
  declarations, or configuration entries.
- Exceptions MUST declare a channel and a reason.
- The normalized contract MUST be deterministic.
- A Blueprint-derived contract MUST preserve the Blueprint profile, version, and
  schema provenance.
- A project snapshot MUST identify unresolved evidence explicitly.

The normalized JSON shape is defined by the
[architecture contract schema](../../schema/architecture-contract-0.1.schema.json).
The generation shape is defined by the
[Architecture Blueprint schema](../../schema/architecture-blueprint-0.1.schema.json).
Facts collected by downstream analyzers use the
[Project Snapshot schema](../../schema/project-snapshot-0.1.schema.json).

## Non-goals

The profile does not validate:

- Clean Architecture layers.
- DDD bounded contexts or tactical patterns.
- Feature-Sliced Design layer ordering.
- Vertical Slice use-case boundaries.
- Angular business-model quality.
- TypeScript imports or filesystem conformance. Those belong to a project
  analyzer and a selected stricter profile.