# Bring an existing codebase into Taiga

Taiga Learning · Worksheet
https://taiga.training/en/lessons/taiga-import/

Use fictional or approved information. Do not put secrets in this worksheet.

## Learning objectives
- Prepare a linked repository for an imported product.
- Distinguish a code defect, a standing instruction, and an analysis error.
- Review proposed initiatives against actual gaps and existing capabilities.

## Exercise
An imported fictional service uses a legacy authorization module. Its replacement is already planned. Write a product instruction that prevents new dependencies on the module. Then identify one repository citation you would inspect in the imported specification.

## Your response
- Scenario and scope:
- Assumptions and open questions:
- Proposed answer or decision, with reasons:

## Verify your response
| Claim or criterion | Evidence or test | Result or gap | Owner |
| --- | --- | --- | --- |
| | | | |
| | | | |
| | | | |

## Next action
- Action, owner, and date:
- When will you review this response?

## Principle to retain
Imported documents describe what the repository shows. The team must identify intended constraints, known defects, and business purpose that code alone cannot establish.

## Sources
- [Taiga docs: Import an existing codebase](https://docs.tai.ga/learn/import-an-existing-codebase/)
- [Taiga docs: Instructions](https://docs.tai.ga/context/instructions/)
- [Taiga docs: Product documents](https://docs.tai.ga/learn/product-documents/)

This worksheet supports learning. Completing it does not itself authorize a production change.