Skip to main content

Smart Engineering Overview

Smart Engineering supports the code modernization journey. You register a repository, index its source code, review the insights, run processes that generate documentation and backlog artifacts, and use the results to browse documentation, technical graphs, logs, and usage metrics.

Two agent-driven workflows sit on top of that foundation:

  • Agentic Chat — a conversational workspace where an agent answers questions about a repository, runs repeatable workflows, and proposes changes you approve inline. This is the screen the application opens after sign-in.
  • Code Modernization — a guided chat that uses completed documentation to analyze the current application, prepare a modernization plan, and generate files for a new application.

What you see depends on the active organization, the repository status, the available process options, and the permissions assigned to your account.

When to use​

  • Document existing systems from source code.
  • Understand structure, dependencies, languages, and code volume.
  • Generate technical documentation, diagrams, and backlog artifacts.
  • Investigate technical relationships in the repository graph.
  • Ask an agent about a repository or run a standardized workflow against it.
  • Recover knowledge about a legacy or poorly documented system.

Before you start​

  • Confirm the active organization.
  • Make sure the correct repository will be created or selected.
  • Prepare the source code as a .zip file or have Git repository access.
  • Confirm that your account can access the module and run processes.

Access​

The app uses the authentication and permission model configured for the environment. When sign-in is required, unauthenticated users are redirected to the login screen. After sign-in, the app validates the active session before exposing protected screens.

If your organization or module access is missing, contact the workspace administrator or project manager before creating repositories.

The sidebar groups the module into sections:

  • Agentic — Chat. Opens Agentic Chat; the Personalize entry inside it manages custom agents and the Recipe Engine.
  • Repositories — view all repositories and create a new one.
  • Modernization — Code Modernization projects and New Modernization.
  • Administration — API Keys and Cost Explorer.

The header exposes global controls, the organization selector, and the command palette. The command palette (search screens and actions) can open navigation, agentic, personalize, modernization, current-repository, and administration entries, depending on context and permissions.

Repository workspace​

The repository workspace is available at /repositories/:repositoryId. It shows a header, breadcrumb, current status, and tabs for the repository lifecycle:

  • Overview
  • Indexing
  • Insights
  • Source Code
  • Processes
  • Documentation
  • Graph
  • Settings

Some tabs stay locked until source code or pre-analysis exists. Cost Explorer is in the Administration area, not a workspace tab.

Step by step​

  1. Sign in and confirm the active organization.
  2. Create or open a repository.
  3. Open Indexing and connect a Git repository or upload a .zip file.
  4. Wait for processing and confirm the pre-analysis; review Insights.
  5. Create a process and select the outputs you need.
  6. Monitor status, logs, and available actions.
  7. Read the generated documentation.
  8. Start a Code Modernization project when you want to plan and generate a new application.
  9. Use Agentic Chat to ask questions or run workflows against the repository.
  10. Explore the graph, references, and code inspector for technical context.
  11. Review Cost Explorer, or download the result package, when needed.

Expected result​

At the end of the flow, the repository should have processed code, available insights, one or more executed processes, generated documentation, and graph references. Code Modernization projects keep the plan, documents, and generated files available for review or download.

See also​