TL;DR
Tandem/dual-VHH CAR concept surface. Use for architecture planning, then inspect isolated-pair pose signals in CAR Interface Assessment and verify binding experimentally.
Use it / Skip it
This is a specialized design surface that remains available for project-specific work, but it is no longer the main platform narrative. Use the Workspace modules for daily intake, triage, scoring, and review.
Use when
A project specifically needs this format, constraint, or legacy flow and the responsible owner has confirmed the backend path for the run.
Don't use for
Do not use it as the default antibody discovery path. For current production work, start from NGS Pool, Semi-de-novo, Interface, Affinity, RFantibody, or CAR Interface Assessment.
Inputs
- Target or parent
- The antigen, parent binder, construct context, or structural constraint required by the page.
- Design settings
- Format-specific parameters such as epitope, framework, count, construct components, linker, or backend.
- Owner confirmation
- For partial/WIP pages, confirm the execution path before promising a wet-lab handoff.
Outputs
- Configuration
- A structured record of the design intent and selected parameters.
- Run or preview
- Available only where the backend is wired; otherwise treat the page as planning UI.
- Handoff note
- The next module or manual review needed before candidate decisions.
Walkthrough
1. Confirm this specialized page is the right entry point for the project
Confirm this specialized page is the right entry point for the project.
2. Fill only the parameters that are meaningful for the current biological question
Fill only the parameters that are meaningful for the current biological question.
3. Check whether the backend is wired before interpreting a submitted run as real work
Check whether the backend is wired before interpreting a submitted run as real work.
4. Move promising sequences or structures back to Interface, Affinity, Compare, or CAR Interface Assessment for evidence review
Move promising sequences or structures back to Interface, Affinity, Compare, or CAR Interface Assessment for evidence review.
Under the hood
- Backend status varies by specialized module.
- Some pages have UI and API stubs ahead of full orchestration.
- Current production evidence should be anchored in persisted jobs and exported artifacts.
Worked example
Pitfalls
- A visible form is not proof that the end-to-end backend is production ready.
- Do not bypass evidence review just because a specialized module produced an attractive preview.
- Keep the module owner in the loop for WIP or partial flows.