124 lines
5.4 KiB
Markdown
124 lines
5.4 KiB
Markdown
# Реальный порядок реализации
|
||
|
||
## Phase 1 — Semantic Core
|
||
|
||
1. `packages/sir`
|
||
2. `rust/crates/bsl-parser`
|
||
- deterministic BSL parser;
|
||
- JSON CLI contract for Python semantic-kernel integration.
|
||
3. `packages/semantic-kernel`
|
||
- current Python parser remains compatible;
|
||
- consumes Rust parser JSON as canonical BSL parse source when the CLI is configured or auto-discovered;
|
||
- metadata object to BSL module links via `CONTAINS`.
|
||
4. `packages/projection-engine`
|
||
5. `packages/incremental-indexer`
|
||
|
||
## Phase 2 — Object Runtime
|
||
|
||
1. `packages/one-c-normalizer`
|
||
- BSL source normalization;
|
||
- XML metadata extraction for core 1C objects.
|
||
2. `packages/semantic-versioning`
|
||
3. `packages/semantic-search`
|
||
4. `packages/impact-engine`
|
||
5. `packages/review-engine`
|
||
|
||
## Phase 3 — Runtime Intelligence
|
||
|
||
1. `runtime-overlays`
|
||
2. `transaction-topology`
|
||
3. `query-intelligence`
|
||
4. `ui-semantics`
|
||
5. `integration-topology`
|
||
6. `job-topology`
|
||
|
||
## Phase 4 — Knowledge System
|
||
|
||
1. global/workspace/project knowledge; ✅
|
||
2. BSP/vendor docs; ✅
|
||
3. pattern mining; ✅
|
||
4. knowledge coverage; ✅
|
||
5. AI answer policy. ✅
|
||
|
||
## Phase 5 — Collaboration
|
||
|
||
1. users/workspaces/projects; ✅
|
||
2. tasks/sessions; ✅
|
||
3. comments/discussions; ✅
|
||
4. activity feed; ✅
|
||
5. ownership. ✅
|
||
|
||
## Phase 6 — Governance/Operations
|
||
|
||
RBAC ✅, privacy ✅, AI usage ✅, jobs ✅, observability ✅, reports ✅, marketplace ✅, licensing ✅, admin ✅.
|
||
|
||
## Phase 7 — 1C IDE / Authoring
|
||
|
||
Reference workflow: берём лучшие рабочие паттерны 1С Конфигуратора, но реализуем их как современную AI IDE. Обязательны дерево конфигурации, вкладки открытых объектов, режимы модуль/форма/свойства/события, инспектор, нижние панели проблем/output/diff и быстрый поиск. Дополнительно SFERA должна объединять версии, документацию, знания, обучение, audit и guarded apply.
|
||
|
||
1. BSL editor foundation:
|
||
- syntax highlighting;
|
||
- diagnostics;
|
||
- outline;
|
||
- go to definition;
|
||
- find references;
|
||
- symbol search.
|
||
2. Semantic autocomplete:
|
||
- current procedure/function context;
|
||
- local variables and parameters;
|
||
- object attributes;
|
||
- tabular sections and columns;
|
||
- form elements and commands;
|
||
- known 1C platform APIs;
|
||
- mixed Russian/English 1C syntax.
|
||
3. AI pair programmer:
|
||
- code continuation;
|
||
- procedure/function generation;
|
||
- query generation;
|
||
- register movement generation;
|
||
- command/form handler generation;
|
||
- explanation of proposed code.
|
||
4. 1C object designer:
|
||
- create/update document/catalog/register/common module metadata;
|
||
- create/update attributes and tabular sections;
|
||
- create/update commands, forms, form elements and reports.
|
||
5. Semantic diff and guarded apply:
|
||
- preview every manual or AI change;
|
||
- impact analysis before apply;
|
||
- review findings before apply;
|
||
- privacy/RBAC checks;
|
||
- object-level version record;
|
||
- rollback point.
|
||
6. IDE-grade UX:
|
||
- editor workspace;
|
||
- object tree;
|
||
- mode bar: module/form/properties/events/versions/docs/knowledge/training;
|
||
- properties inspector;
|
||
- form/report designer;
|
||
- terminal/command palette;
|
||
- AI assistant panel;
|
||
- problems/references/output panels.
|
||
|
||
7. Documentation/knowledge/training inside IDE:
|
||
- docs linked to objects, forms, reports, events and routines;
|
||
- project/vendor/BSP knowledge available next to the code;
|
||
- team patterns, decisions and examples surfaced by current context;
|
||
- learning hints for the selected object and available variables;
|
||
- search across code, metadata, docs, versions and discussions.
|
||
|
||
## Frontend/UI Gate
|
||
|
||
Перед началом UI-этапа перечитать и применить актуальные требования:
|
||
|
||
- `docs/design-system.md`
|
||
- `docs/codex-ui-guidelines.md`
|
||
- `docs/ui-ux-roadmap.md`
|
||
- `docs/component-architecture.md`
|
||
- `docs/frontend-stack.md`
|
||
- `prompts/system-frontend-architect.md`
|
||
- `prompts/ui-generation-prompt.md`
|
||
|
||
Ключевой принцип: SFERA UI должен ощущаться как современная Enterprise AI IDE / Operating System для 1С, а не legacy CRM. Каждый экран обязан иметь AppShell-compatible layout, loading/error/empty/permission states, адаптивность, права доступа, audit trail для важных действий, таблицы с фильтрами/saved views/bulk actions и AI token/cost impact для AI-действий. Для authoring-экранов обязательны editor/object tree/properties inspector/problems/diff/preview/apply states.
|
||
|
||
Язык UI/команд: русский по умолчанию, но каждый пользовательский экран должен иметь выбор английского интерфейса. Команды в интерфейсе также проектируются с русским вариантом по умолчанию и английским вариантом как доступным режимом. 1С-код может смешивать русские и английские ключевые слова в одном тексте; parser/review/UI не должны считать это ошибкой.
|