Improve New Engineer Readiness
New engineer의 시작점, check sequence, expected output format 이해와 senior escalation 전 first-pass analysis 준비 지원.
SoC Work Support System
검증된 SoC workflow 전파와 약한 지점 가시화
AWARE-AI SAA: 조직 안의 best proven SoC workflow를 SoC Work Area, SoC Task Flow, Agent Role, Recommended Skill Pack 중심의 reusable procedure로 정리하는 on-premise SoC work support system.
New engineers follow clearer work paths.
Senior engineers spend less time on repeated first-pass support.
Teams expose missing inputs, weak evidence gates, unclear handoffs, and repeated bottlenecks.
Product Value
Best proven SoC workflow를 reusable task flow로 전환
SoC development: spec, RTL, testbench, script, tool option, log, review rule 사이 관계 이해가 필요한 작업.
SAA: 조직의 proven source-backed workflow를 구조화해 team의 반복 사용과 개선을 지원하는 체계.
Reduce Repetitive Senior Support
반복 설명, first-pass log triage, script draft, review checklist preparation 감소와 senior engineer의 technical judgment 집중 지원.
Preserve Project-specific Know-how
흩어진 project knowledge를 reusable procedure, project profile, checklist, work history로 남깁니다.
Expose Workflow Weak Spots
Missing input, weak evidence gate, unclear handoff, repeated bottleneck, inconsistent checklist practice 가시화.
SAA의 역할: engineering preparation 지원.
Final root-cause judgment, design approval, verification approval, sign-off acceptance, technical priority decision은 engineer 결정 사항.
Use Cases
Common SoC engineering task를 실무적으로 지원
SAA: blank page에서 시작하는 generic chat이 아니라 project reference, standard work procedure, execution menu, work history 기반의 반복 업무 지원 체계.
각 request: SoC Work Area, SoC Task Flow, Agent Role, Recommended Skill Pack, Required Inputs, Capability Checklist, Evidence Gates 명시 가능.
Fail signature, likely cause, related test, next check 후보 요약.
Run step, directory structure, required input, expected output의 project convention 기준 설명.
Spec/RTL requirement, unclear item, module/interface/parameter, checklist candidate 정리.
Tcl, Python, shell, Perl, test scenario, checker idea, SVA candidate 초안의 engineer review용 준비.
RFI candidate field가 final SOW, approved profile, customer-confirmed delivery profile 없이 runtime truth가 되지 않도록 boundary 준비.
Recommended Skill Pack, Profile Required Before, Boundary / Non-claims 확인과 request context 명확화.
Project ReferencesSpecs, logs, scripts, guides, review rules, project documents의 reference base 사용.
Standard ProceduresLog triage, script drafting, review preparation, issue summary의 reusable procedure 정리.
Work HistoryRequest metadata, result location, latency, token usage, follow-up information으로 traceability를 남깁니다.
Approval ProfilesCustomer-selected tool, filelist, command wrapper의 final SOW, approved project profile, 또는 customer-confirmed delivery profile 이후 runtime source 승격.
Agentic ContinuityRepo-contained LLM wiki, SAA Studio request builder, evidence taxonomy, handoff history: source truth 대체가 아닌 resume/review 지원.
SAA Studio Preview
SoC Support Request 구성 미리보기
SAA Studio: homepage에서 실제 request 제출이나 실행을 하는 화면이 아니라, SoC support request 구성 구조를 보여주는 request-builder preview.
완성본 UI가 아니라 customer terminology, allowed Work Area, default Task Flow, Agent Role, Recommended Skill Pack, Project Links/PMS posture에 맞춘 customization 가능 concept.
Request Setup
SoC Work AreaRTL Integration
SoC Task FlowInterface impact review
Agent RoleReviewer + Builder support
Recommended Skill Packsoc-rtl-integration
Project LinkDry-run / review only
Dropdown labels, defaults, project links, and role names are customizable through RFI/SOW/profile work.
Selected Skill Pack
soc-rtl-integration
Required Inputs
Spec slice, RTL filelist, interface notes, known constraints, reviewer intent.
Capability Checklist
Map affected modules, interfaces, parameters, dependencies, and review questions.
Evidence Gates
Record source refs, changed assumptions, validation state, blocker/advisory notes, and handoff owner.
Profile Required Before
Customer tool paths, simulator commands, private project roots, and apply permissions remain profile-driven.
Boundary / Non-claims
No browser-side execution, source apply, signoff, tapeout, regression closure, or customer acceptance claim.
Generated Request Preview
/saa-op request
work_area: RTL Integration
task_flow: Interface impact review
role: Reviewer + Builder support
skill_pack: soc-rtl-integration
evidence: source refs + handoff summary
mode: preview only, operator confirmation requiredNo submit in homepage preview
Homepage preview: real request submit 아님.
Browser: tool 실행, file edit, validator run, source apply 없음.
Execution, validation evidence, handoff 담당: pi-agent/operator confirmation.
Adoption Process
설치 조건과 sensitive workflow를 나누어 단계적으로 도입
SAA: one-click deployment가 아니라 customer server environment, security rule, SoC development procedure, runtime/tooling posture, SoC Work Area/SoC Task Flow/profile needs, acceptance evidence에 맞춘 적용.
RFI question groups: discovery input.
Runtime truth promotion: approved source 필요.
Schedule: fixed promise 아님.
Team size, project count, separated security zone, approval process, legacy automation complexity에 따른 조정 대상.
LLM wiki continuity이전 결정과 handoff를 찾는 retrieval aid.
Docs, reports, configs, evidence, tracking과 cross-check 필요.
Docs, reports, configs, evidence, tracking과 cross-check 필요.
SAA Studio request builderBrowser에서 SoC Support Request 구성과 confirmation context 작성.
Browser-side execution 권한 없음.
Browser-side execution 권한 없음.
Evidence taxonomypass, fail, blocked, skipped, advisory 구분.
Skipped/advisory를 pass처럼 설명 금지.
Skipped/advisory를 pass처럼 설명 금지.
Security
External AI service로 SoC design data를 보내기 어려운 환경을 전제로 설계
SAA: internal EDA server와 LLM server 구조, controlled access, local endpoint, work history logging을 전제로 하는 secure in-house deployment 목표.
EDA server
- SoC design data, script, log, automation client의 customer-controlled EDA environment 보관.
- User의 EDA-side local endpoint 호출.
LLM server
- Internal language processing engine의 vLLM-compatible API 운영.
- DGX-side internal vLLM port의 외부 직접 노출 금지.
Access control
- Shared SSH tunnel, IP allowlist, optional API key의 customer policy 기반 조정.
- API key: committed file이 아니라 environment variable 취급.
Committed homepage and delivery materials follow the no-record matrix: no secrets, license data, private URLs, customer IP, RFQ prices, raw project data, model weights, endpoint values, or hardcoded customer paths.
Contact / RFI
Non-security RFI에서 시작해 secure SoC workflow customization으로 확장
SAA adoption: customer server environment, security policy, repeated SoC work procedure, runtime/tooling posture, SoC Work Area/SoC Task Flow/profile needs, acceptance evidence 이해에서 시작.
먼저 installation/integration condition 확인, 이후 customer approval 기반 project-sensitive workflow 반영.
- Request Non-security RFI: delivery/system/environment, server, network, account, installation, operation condition 확인
- Discuss Secure SoC Workflow Customization: runtime/model/tooling, project profile, SoC Work Area, SoC Task Flow, Agent Role, Project Links, security/export/acceptance/docs-support 확인
- Confirm promotion boundary: final SOW, approved project profile, or customer-confirmed delivery profile before runtime truth
- Confirm no-record boundary: secrets, license data, raw customer IP, RFQ prices, raw RTL/IP/spec logs, model weights, endpoint values 제외
- Ask for a phased adoption plan: team/project scope와 approval path에 맞춰 범위 논의
RFI Contact
caio@aware-ai.kr
Start with server environment, security policy, team size, repeated SoC tasks, and first adoption area.