francy51
14a7773504
Create unified disclosure statement to organize footnote disclosures separate from primary financial statements. Disclosures are now grouped by type (tax, debt, securities, derivatives, leases, intangibles, ma, revenue, cash_flow) in a dedicated statement type for cleaner UI presentation.
30 lines
1.4 KiB
Markdown
30 lines
1.4 KiB
Markdown
# AGENTS.md
|
|
|
|
## Task Completion Requirements
|
|
|
|
- All of `bun fmt`, `bun lint`, and `bun typecheck` must pass before considering tasks completed.
|
|
- NEVER run `bun test`. Always use `bun run test` (runs Vitest).
|
|
- Always use the tea CLI for repository actions.
|
|
|
|
## Project Snapshot
|
|
|
|
Neon Code is a comprehensive portfolio management and equity research platform. It helps analysts manage their portfolio, organize research and view individual stocks.
|
|
|
|
This repository is a VERY EARLY WIP. Proposing sweeping changes that improve long-term maintainability is encouraged.
|
|
|
|
## Core Priorities
|
|
|
|
1. Performance first.
|
|
2. Reliability first.
|
|
3. Keep behavior predictable under load and during failures (session restarts, reconnects, partial streams).
|
|
|
|
If a tradeoff is required, choose correctness and robustness over short-term convenience.
|
|
|
|
## Maintainability
|
|
|
|
Long term maintainability is a core priority. If you add new functionality, first check if there are shared logic that can be extracted to a separate module. Duplicate logic across multiple files is a code smell and should be avoided. Don't be afraid to change existing code. Don't take shortcuts by just adding local logic to solve a problem.
|
|
|
|
## Documentation
|
|
|
|
Documentation should be located in /doc folder. Make sure that the docs are up to date and ensure that robust architecture and strong coding patterns are propagated throughout.
|