Entity Codes and References

Every entity in your project gets a short, human-readable code the moment it is created — F-002 for a feature, US-014 for a user story, PG-005 for a page. Codes are sequential per project, stable for the life of the entity, and shown throughout the UI. They give you (and the agent) an unambiguous way to refer to any entity, even when two entities have similar names.

The code prefixes

Schema columns don't get their own code — they are addressed relative to their parent table as table code + dot + column name:

• T-001.email — the email column on table T-001
• T-002.status — the status column on table T-002

Referencing entities in agent chat

The agent understands four ways of pointing at your project's entities:

1. #table — focus on an entity type

Type # to insert a table reference, e.g. #features or #user-stories. This tells the agent which kind of entity you want to operate on:

• "Create three #user-stories for the search feature"
• "Which #pages are missing sections?"

2. @table:identifier — explicit record references

Type @ followed by a table name and colon to open a record picker, e.g. @pages: then choose one. The reference renders as a chip in your message, so there's no ambiguity about which record you mean:

• @pages:PG-002 — a specific page
• @schema_table:T-001.email — a specific column

3. Bare codes in plain text

You don't need any special syntax — just use the code in a normal sentence and the agent resolves it. Codes must be uppercase:

• "Combine PG-002 and PG-003 into a single settings page"
• "Delete US-014"
• "Move AC-003 to F-005"

4. Bare column references

Column references work the same way in plain text:

• "Rename T-002.status to state"
• "Make T-001.email NOT NULL"

Codes in agent replies

The agent uses the same codes in its own responses — "I've split F-002 into F-007 and F-008" — so you can always trace exactly which entities were touched and reference them in your next message.

Tips

• Prefer codes over names when precision matters. "Delete the login page" is ambiguous if you have PG-004 Login and PG-009 Admin Login; "Delete PG-009" is not.
• Codes are stable. Renaming an entity never changes its code, so codes in older conversations stay valid.
• Codes are references, not names. They identify entities; the agent won't bake them into entity names it generates.