Q&A

Deletion impact

These questions cover the cascading effects of renaming or deleting Accounts, Symbols, positions, attachments, and Confluence.

Failed Account rename

An Account rename failed, leaving some linked files changed and others unchanged.

Renaming an Account rewrites the Account, Symbols, and position references one by one, with no rollback. Changes completed before a failure remain in place.

→ Accounts and Symbols · Account and Platform Fields

Account deletion scope

The Account deletion list also includes Symbols, positions, or even a Platform.

Delete Account? removes the whole downstream relationship.

Platform names that differ only by case can confuse sharing detection.

→ Accounts and Symbols

Symbol deletion scope

Linked positions disappeared when I deleted a Symbol.

Confirm Delete trashes the linked positions before the Symbol file.

Position attachments are not cleaned up.

→ Accounts and Symbols · Charts, Attachments, and OCR

Orphaned attachments

I deleted a position, but its attachments remain in the vault.

Deleting a position directly moves only its file. It does not clean up exclusive files under LucrJournal/attachments/.

Remove unwanted attachments from the position interface first.

→ Position Lifecycle · Charts, Attachments, and OCR

Broken body image

A Markdown body image broke after I deleted an attachment.

Delete attachment removes the frontmatter reference but does not scan the Markdown body. An exclusive physical file may be deleted even while the body still embeds it.

→ Charts, Attachments, and OCR · Local files and Markdown

A Playbook has a broken link after I deleted Confluence.

Deleting Confluence from Analysis cleans position links but does not rewrite Playbook bodies.

Confirm that no Playbook still references it before deleting.

→ Context Notes · Playbooks and Criteria